From: Andrey <butirsky@gmail•com>
To: git@vger•kernel.org
Subject: bash completion bug: "symbolic-ref" subcommand doesn't complete
Date: Thu, 12 Mar 2026 19:14:16 +0300 [thread overview]
Message-ID: <c1e0c05b-c767-4fcc-859a-4da6b90c4497@gmail.com> (raw)
Bash can't complete some commands, e.g. symbolic-ref, bugreport, maybe
others.
These commands are not seen in the completion output:
|$ git #press Tab
add blame citool diff gitk
log prune refs restore
show submodule
am branch clean difftool
grep maintenance pull remote revert
show-branch switch
apply bundle clone fetch gui
merge push repack rm
sparse-checkout tag
archive checkout commit format-patch help
mergetool range-diff replace scalar
stage whatchanged
backfill cherry config fsck init
mv rebase request-pull send-email
stash worktree
bisect cherry-pick describe gc
instaweb notes reflog reset shortlog
status |
|
|
There is no such problem with Zsh.
[System Info]
GNU bash, version 5.3.0(1)-release (x86_64-redhat-linux-gnu)
git version 2.53.0
rust: disabled
gettext: enabled
libc info: glibc: 2.42
next reply other threads:[~2026-03-12 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 16:14 Andrey [this message]
2026-03-12 16:21 ` bash completion bug: "symbolic-ref" subcommand doesn't complete Junio C Hamano
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=c1e0c05b-c767-4fcc-859a-4da6b90c4497@gmail.com \
--to=butirsky@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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