From: Shawn Pearce <spearce@spearce.org>
To: git@vger.kernel.org
Subject: bash completion in backticks partially broken
Date: Sun, 5 Nov 2006 04:05:40 -0500 [thread overview]
Message-ID: <20061105090540.GA4843@spearce.org> (raw)
So an annoying feature of bash appears to be that it won't really
provide completion on backtick'd commands.
For example I can complete "git merge-base ma" just fine as is, but
if I toss it into backticks say "git update-ref M `git merge-base ma"
then I can't complete "ma" out to "master" anymore.
A little bit of debugging appears to show that bash is invoking the
completion hook for the outermost command; that is we are looking
for parameters for update-ref and not merge-base.
I think I could rewrite a good part of git-completion.bash to
support this use. But it won't work for "echo `git merge-base ma"
as the outermost command is echo and we don't have a Git completion
hook registered for that command.
This is really annoying when it comes to less contrived examples.
I find myself forming odd pipelines with commit-tree, update-ref,
mktree, lstree, sed, rev-list, etc. and always keep bumping up on
the limitations of git-completion.bash.
Any suggestions? How often do bash users try to use backticks to
call Git commands, only to find bash isn't being as helpful as it
should be?
--
next reply other threads:[~2006-11-05 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 9:05 Shawn Pearce [this message]
2006-11-05 9:48 ` bash completion in backticks partially broken Junio C Hamano
2006-11-05 10:26 ` Shawn Pearce
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=20061105090540.GA4843@spearce.org \
--to=spearce@spearce.org \
--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;
as well as URLs for NNTP newsgroup(s).