From: Andrey <butirsky@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: bash completion bug: "symbolic-ref" subcommand doesn't complete
Date: Thu, 12 Mar 2026 19:47:47 +0300 [thread overview]
Message-ID: <57252c1e-69e6-4953-beb3-3cfd41cab857@gmail.com> (raw)
In-Reply-To: <xmqqikb1ggri.fsf@gitster.g>
You forgot to mention the main thing:
/usr/share/bash-completion/completions/git:
...
# GIT_COMPLETION_SHOW_ALL_COMMANDS
#
# When set to "1" suggest all commands, including plumbing commands
# which are hidden by default (e.g. "cat-file" on "git ca<TAB>").
Thanks for the tip, though.
On 3/12/26 19:21, Junio C Hamano wrote:
> Isn't this working as intended?
>
> Our general principle is that the plumbing commands are not designed
> to be "typed" by end-user to use interactively, and cat-file,
> commit-tree, etc. are not completed to reduce cluttering
prev parent reply other threads:[~2026-03-12 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 16:14 bash completion bug: "symbolic-ref" subcommand doesn't complete Andrey
2026-03-12 16:21 ` Junio C Hamano
2026-03-12 16:26 ` Andrey
2026-03-12 16:47 ` Andrey [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=57252c1e-69e6-4953-beb3-3cfd41cab857@gmail.com \
--to=butirsky@gmail.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