Re: bash completion in backticks partially broken

[Junio C Hamano <junkio@cox.net>]

Shawn Pearce <spearce@spearce.org> writes:

> 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?

I am more interested in why you would even need to use
combinations of such low-level commands in day-to-day workflow.

If they are often-needed patterns, you would have scripted them
already, so completion would not be an issue for you.  So I am
assuming these are ad-hoc one-shot needs.

While it is satisfying to know that things you would want to do
can be scripted even for one-shot use (which is how git is
designed to, and it shows that the design goal has been
achieved), maybe it's a sign that we are giving you too much
flexibility?  Under less capable/flexible system that puts you
in a straightjacket, you would not even be tempted to do oddball
things to begin with...