Re: possible bug in autocompletion

2012-09-19 Thread Jeff King
On Thu, Sep 20, 2012 at 01:08:29AM +0200, Felipe Contreras wrote: > On Wed, Sep 19, 2012 at 9:55 PM, Jeff King wrote: > > > I have no idea if that internal to bash's filename completion, or if > > there is some easy facility offered to programmable completions to do > > the same thing. I don't

Re: possible bug in autocompletion

2012-09-19 Thread Jeff King
On Wed, Sep 19, 2012 at 08:23:01PM +0200, Felipe Contreras wrote: > >> Care to wrap it up in a patch? > > > > I'm trying to, but unfortunately "\n" gets converted to "\\n", so it > > doesn't get separated to words. Any ideas? > > Actually, this seems to do the trick: > > local words IFS=$'

Re: possible bug in autocompletion

2012-09-19 Thread Felipe Contreras
On Wed, Sep 19, 2012 at 8:16 PM, Felipe Contreras wrote: > On Wed, Sep 19, 2012 at 7:43 PM, Jeff King wrote: >> On Wed, Sep 19, 2012 at 07:08:09PM +0200, Felipe Contreras wrote: >> >>> On Tue, Jul 17, 2012 at 2:12 PM, Jeff King wrote: >>> >>> > --- a/contrib/completion/git-completion.bash >>> >

Re: possible bug in autocompletion

2012-09-19 Thread Felipe Contreras
On Wed, Sep 19, 2012 at 7:43 PM, Jeff King wrote: > On Wed, Sep 19, 2012 at 07:08:09PM +0200, Felipe Contreras wrote: > >> On Tue, Jul 17, 2012 at 2:12 PM, Jeff King wrote: >> >> > --- a/contrib/completion/git-completion.bash >> > +++ b/contrib/completion/git-completion.bash >> > @@ -261,7 +261,1

Re: possible bug in autocompletion

2012-09-19 Thread Junio C Hamano
Felipe Contreras writes: > On Tue, Jul 17, 2012 at 2:12 PM, Jeff King wrote: > >> --- a/contrib/completion/git-completion.bash >> +++ b/contrib/completion/git-completion.bash >> @@ -261,7 +261,12 @@ __gitcomp () >> __gitcomp_nl () >> { >> local IFS=$'\n' >> - COMPREPLY=($(compgen

Re: possible bug in autocompletion

2012-09-19 Thread Jeff King
On Wed, Sep 19, 2012 at 07:08:09PM +0200, Felipe Contreras wrote: > On Tue, Jul 17, 2012 at 2:12 PM, Jeff King wrote: > > > --- a/contrib/completion/git-completion.bash > > +++ b/contrib/completion/git-completion.bash > > @@ -261,7 +261,12 @@ __gitcomp () > > __gitcomp_nl () > > { > >

Re: possible bug in autocompletion

2012-09-19 Thread Felipe Contreras
On Tue, Jul 17, 2012 at 2:12 PM, Jeff King wrote: > --- a/contrib/completion/git-completion.bash > +++ b/contrib/completion/git-completion.bash > @@ -261,7 +261,12 @@ __gitcomp () > __gitcomp_nl () > { > local IFS=$'\n' > - COMPREPLY=($(compgen -P "${2-}" -S "${4- }" -W "$1" -- "$

Re: possible bug in autocompletion

2012-07-17 Thread Jeff King
On Tue, Jul 17, 2012 at 11:10:39AM +0200, Jeroen Meijer wrote: > We have a tag name with some special characters. The tag name is > 'Build%20V%20${bamboo.custom.jiraversion.name}%20Build%20721'. In > somecases where autocompletion is used an error is given, such as > 'bash: Build%20V%20${bamboo.cu

possible bug in autocompletion

2012-07-17 Thread Jeroen Meijer
We have a tag name with some special characters. The tag name is 'Build%20V%20${bamboo.custom.jiraversion.name}%20Build%20721'. In somecases where autocompletion is used an error is given, such as 'bash: Build%20V%20${bamboo.custom.jiraversion.name}%20Build%20721: bad substitution'. This can be