Re: [PATCH 1/2] completion: handle unstuck form of base git options
- From
SZEDER Gábor <szeder@ira.uka.de>
- Date
- Jun 22, 2013, 12:35 UTC
- Message-ID
- <20130622123533.GJ20052@goldbirke>
- In-Reply-To
- <20130622123033.GI20052@goldbirke>
On Sat, Jun 22, 2013 at 02:30:33PM +0200, SZEDER Gábor wrote:
Show 12 quoted lines
> Hi, > > On Sat, Jun 22, 2013 at 12:25:17PM +0100, John Keeping wrote: > > git-completion.bash's parsing of the command name relies on everything > > preceding it starting with '-' unless it is the "-c" option. This > > allows users to use the stuck form of "--work-tree=<path>" and > > "--namespace=<path>" but not the unstuck forms "--work-tree <path>" and > > "--namespace <path>". Fix this. > > I never use these commands, so I looked up what --namespace means. > While doing so I noticed that --exec-path takes a path just like these > options, so that option should be handled similarly as well.
Never mind, I misunderstood the docs: --exec-path either takes a path as --exec-path=<path> or it doesn't take one at all, but there is no '--exec-path <path>'.
Gábor