From: Thomas Rast <trast@student.ethz.ch>
To: Mathieu CLAVEL <math.clavel@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: [BUG ?] completion of stash name with git stash
Date: Thu, 19 Jan 2012 17:18:04 +0100 [thread overview]
Message-ID: <87lip3mzsz.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <loom.20120119T141601-606@post.gmane.org> (Mathieu CLAVEL's message of "Thu, 19 Jan 2012 13:21:53 +0000 (UTC)")
Mathieu CLAVEL <math.clavel@gmail.com> writes:
> I'm using mysgit 1.7.8 on XP.
>
> I think the stash name completion has a problem.
> I don't know if it's a problem from my system, mysgit or git.
>
> Here are the steps to reproduce (you need to have at least 2 stashed commits).
> '+ tab =>' means using the tab to autocomplete the current command. Left part is
> before completion, right tab is after completion.
>
> $ git stash list
> stash@{0}: WIP on feature/preservation_offres: 7f2c9a8 import.cmd : import par
> lot de 10.000 contrats
> stash@{1}: WIP on feature/echeancier: ddb7bb0 Mockito : 1.8.5 -> 1.9.0
>
> $ git stash drop '+ tab =>' $ git stash drop stash@{
>
> $ git stash drop stash@{0 '+ tab =>' $ git stash drop stashstash@{0}
>
> I don't know if it's relevant, but I also have 'git flow' and 'git flow
> completion' installed, and as said in a previous thread, 'git flow completion'
> isn't working with alias [2].
This works for me using git completion as shipped with v1.7.9-rc2 and
bash 4.2.10. Double-tabbing at 'git stash drop ' prints a list of
stashes as expected. Which bash version are you using?
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-01-19 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 13:21 [BUG ?] completion of stash name with git stash Mathieu CLAVEL
2012-01-19 16:18 ` Thomas Rast [this message]
2012-01-19 16:34 ` Mathieu CLAVEL
2012-01-19 18:14 ` Thomas Rast
2012-01-23 8:36 ` Mathieu CLAVEL
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lip3mzsz.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=math.clavel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).