From: Michael Schubert <mschub@elegosoft.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] git-completion: offer references for 'git reflog'
Date: Tue, 04 Oct 2011 21:34:25 +0200 [thread overview]
Message-ID: <4E8B5FC1.3080902@elegosoft.com> (raw)
In-Reply-To: <7v7h4kd6vg.fsf@alter.siamese.dyndns.org>
On 10/04/2011 07:05 PM, Junio C Hamano wrote:
> Michael Schubert <mschub@elegosoft.com> writes:
>
>> On 09/25/2011 12:42 PM, Michael Schubert wrote:
>>> 'git reflog <ref>' is a valid command, therefore offer reference
>>> completion.
>>>
>>> Signed-off-by: Michael Schubert <mschub@elegosoft.com>
>>> ---
>>> contrib/completion/git-completion.bash | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
>>> index 8648a36..63d0f08 100755
>>> --- a/contrib/completion/git-completion.bash
>>> +++ b/contrib/completion/git-completion.bash
>>> @@ -1774,7 +1774,7 @@ _git_reflog ()
>>> local subcommand="$(__git_find_on_cmdline "$subcommands")"
>>>
>>> if [ -z "$subcommand" ]; then
>>> - __gitcomp "$subcommands"
>>> + __gitcomp "$subcommands $(__git_refs)"
>>> else
>>> __gitcomp "$(__git_refs)"
>>> fi
>>
>> Ping.?
>
> Personally I think this change will give much less pleasant user
> experience. This is what I currently get:
>
> $ git reflog <TAB>
> delete expire show
> $ git reflog
>
> and after learning the "show" subcommand exists, this is what I would get:
>
> $ git reflog show <TAB>
> Display all 626 possibilities? (y or n)
>
> With your change, I would get:
>
> $ git reflog <TAB>
> Display all 629 possibilities? (y or n)
Yeah, that would be a tradeoff. IMHO the current behaviour is pleasant
for newcomers, but (I guess) most users would rather enjoy "the short form".
> and do not even have a chance to remind myself if the subcommand to drop
> a reflog was "delete" or "remove".
>
> At least when I know that I want to be reminded of refs to $verb (use one
> of the three subcommands I currently get in place of the "$verb"), I can
> say
>
> $ git reflog $verb <TAB>
>
> and at that point, I am willing to wade thru list of 600+ refs.
prev parent reply other threads:[~2011-10-04 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 10:42 [PATCH] git-completion: offer references for 'git reflog' Michael Schubert
2011-10-04 8:48 ` Michael Schubert
2011-10-04 17:05 ` Junio C Hamano
2011-10-04 19:34 ` Michael Schubert [this message]
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=4E8B5FC1.3080902@elegosoft.com \
--to=mschub@elegosoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).