Re: bug in bash completion for git-branch --set-upstream-to on OSX

2015-03-23 Thread Jason Karns
For those curious, the source of the broken behavior is npm's completion script. It is modifying COMP_WORDBREAKS. There are two open issues against npm for this bug. https://github.com/npm/npm/issues/4530 https://github.com/npm/npm/issues/5820 Jason -- To unsubscribe from this list: send the

Re: bug in bash completion for git-branch --set-upstream-to on OSX

2015-03-23 Thread Jason Karns
On Sun, Mar 22, 2015 at 7:06 AM, SZEDER Gábor sze...@ira.uka.de wrote: Hi, Quoting Jason Karns karns...@gmail.com: There appears to be a bug in the bash completion for git-branch when attempting to complete the remote ref argument for --set-upstream-to= When: $ git branch

Re: bug in bash completion for git-branch --set-upstream-to on OSX

2015-03-22 Thread SZEDER Gábor
Hi, Quoting Jason Karns karns...@gmail.com: There appears to be a bug in the bash completion for git-branch when attempting to complete the remote ref argument for --set-upstream-to= When: $ git branch --set-upstream-to=origin/mastTAB I would expect it to complete to: $ git branch

Re: bug in bash completion for git-branch --set-upstream-to on OSX

2015-03-21 Thread Eric Sunshine
On Fri, Mar 20, 2015 at 11:15 AM, Jason Karns karns...@gmail.com wrote: There appears to be a bug in the bash completion for git-branch when attempting to complete the remote ref argument for --set-upstream-to= When: $ git branch --set-upstream-to=origin/mastTAB I would expect it to

bug in bash completion for git-branch --set-upstream-to on OSX

2015-03-20 Thread Jason Karns
There appears to be a bug in the bash completion for git-branch when attempting to complete the remote ref argument for --set-upstream-to= When: $ git branch --set-upstream-to=origin/mastTAB I would expect it to complete to: $ git branch --set-upstream-to=origin/master However, the completion