Re: [PATCH 2/3] Makes the bash completion script try *bash* completions before simple, filetype completions when a git completion is not found. If bash, completions aren't available, the default file completions are used. This, behavior was inspired by Mercurial's bash completion script.
- From
Shawn O. Pearce <spearce@spearce.org>
- Date
- Jan 13, 2009, 16:38 UTC
- Message-ID
- <20090113163816.GR10179@spearce.org>
- In-Reply-To
- <496CBCED.80402@tedpavlic.com>
Ted Pavlic <ted@tedpavlic.com> wrote:
Show 10 quoted lines
> > Second in a series of patches that make bash completions more robust to > different interactive shell configurations and editors. > > > [PATCH 2/3] Makes the bash completion script try *bash* completions > before simple > filetype completions when a git completion is not found. If bash > completions aren't available, the default file completions are used. This > behavior was inspired by Mercurial's bash completion script.
Again, I would have used this as my commit message:
bash-completion: Try bash completions before file completions
Try bash completions before any simple file completions whenever a git completion is not found. This may help users to complete BLAH BLAH BLAH WHAT THE HECK IS THIS GOOD FOR ANYWAY.
Behavior was inspired by Mercurial's bash completion script.
No ack, because I still don't understand why this is a good thing. Yes, I could look it up online in the bash docs. I shouldn't need to go do research like that to understand the justification for a change, it should be better explained in the message.
-- Shawn.