From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Wiktor Mis via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Wiktor Mis <mwiktor023@gmail.com>
Subject: Re: [PATCH v2] completion: complete "git -<TAB>" with short options
Date: Thu, 27 Nov 2025 08:33:30 +0100 [thread overview]
Message-ID: <aSf+yrfJo8dRIkSo@szeder.dev> (raw)
In-Reply-To: <xmqqh5ugmu8d.fsf@gitster.g>
On Wed, Nov 26, 2025 at 12:09:22PM -0800, Junio C Hamano wrote:
> "Wiktor Mis via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > From: Wiktor Mis <mwiktor023@gmail.com>
> >
> > "git" itself has completion for long options and cmds, but not short ones
> >
> > Signed-off-by: Wiktor Mis <mwiktor023@gmail.com>
> > ---
> > Add completion for short options
>
> Will queue with a slight update to the log message. I am unsure if
> we want to limit "-<TAB>" to one-letter options or if we want to
> include the long ones (the latter is what v2 implements), but let's
> see if others have strong opinions.
>
> completion: complete "git -<TAB>" with short options
>
> "git" itself has completion for its long options and subcommands,
> but not for its short options. Add support for them.
It's not just git itself that doesn't have completion for its short
options, but the completion script in general doesn't complete the
short options for anything. The reason being, I think, that it
doesn't save keystrokes and it doesn't really help discoverability
(Well, okay, strictly speaking it does help discoverability in the
sense that 'git -<TAB>' will show the existence of short options, but
since short options don't have self-explanatory names, the users won't
know what those short options are good for. E.g. I just learned from
this patch that the main git command accepts -p and -P options, but I
have no idea what they are doing.)
So overall I'm somewhat negative on this patch and in general on the
direction it takes us, but if we do want to go in this direction, then
it will definitely need more justification than this.
> Signed-off-by: Wiktor Mis <mwiktor023@gmail.com>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
>
> Thanks.
>
> > contrib/completion/git-completion.bash | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> > index 73abea31b4..1705ca3323 100644
> > --- a/contrib/completion/git-completion.bash
> > +++ b/contrib/completion/git-completion.bash
> > @@ -3898,7 +3898,7 @@ __git_main ()
> > ;;
> > esac
> > case "$cur" in
> > - --*)
> > + -*)
> > __gitcomp "
> > --paginate
> > --no-pager
> > @@ -3914,6 +3914,12 @@ __git_main ()
> > --namespace=
> > --no-replace-objects
> > --help
> > + -C
> > + -P
> > + -c
> > + -h
> > + -p
> > + -v
> > "
> > ;;
> > *)
> >
> > base-commit: fd372d9b1a69a01a676398882bbe3840bf51fe72
next prev parent reply other threads:[~2025-11-27 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 6:38 [PATCH] Add completion for short options Wiktor Mis via GitGitGadget
2025-11-25 16:42 ` Junio C Hamano
2025-11-26 16:26 ` [PATCH v2] completion: complete "git -<TAB>" with " Wiktor Mis via GitGitGadget
2025-11-26 20:09 ` Junio C Hamano
2025-11-27 7:33 ` SZEDER Gábor [this message]
2025-11-27 21:59 ` Junio C Hamano
2025-12-07 0:38 ` Junio C Hamano
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=aSf+yrfJo8dRIkSo@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=mwiktor023@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).