From: Junio C Hamano <gitster@pobox.com>
To: Andrey <butirsky@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: bash completion bug: "symbolic-ref" subcommand doesn't complete
Date: Thu, 12 Mar 2026 09:21:53 -0700 [thread overview]
Message-ID: <xmqqikb1ggri.fsf@gitster.g> (raw)
In-Reply-To: <c1e0c05b-c767-4fcc-859a-4da6b90c4497@gmail.com> (Andrey's message of "Thu, 12 Mar 2026 19:14:16 +0300")
Andrey <butirsky@gmail.com> writes:
> Bash can't complete some commands, e.g. symbolic-ref, bugreport, maybe
> others.
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 when the
user does
$ git <TAB>
If zsh completion includes plumbing commands, then zsh completion is
buggy, or those who designed zsh completion did not understand the
general principle ;-).
next prev parent reply other threads:[~2026-03-12 16:21 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 [this message]
2026-03-12 16:26 ` Andrey
2026-03-12 16:47 ` Andrey
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=xmqqikb1ggri.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=butirsky@gmail.com \
--cc=git@vger.kernel.org \
/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