On Tue, Aug 15, 2017 at 1:09 PM, Igor Djordjevic
<igor.d.djordje...@gmail.com> wrote:
> Hi Jason,
>
> On 15/08/2017 16:26, Jason Karns wrote:
>> I have a git repo that shows a different branch in
>> `.git/refs/remotes/origin/HEAD` than is reported by `git remote show
&
continues to report `master` as the remote's HEAD.
Thanks,
Jason Karns
> We could discern between more than just empty vs. non-empty state of
> the environment variable, e.g.:
>
> - if empty/unset, then include "DWIM" suggestions.
> - if set to 'config', then query the 'completion.checkoutNoGuess'
>configuration variable, and omit "DWIM" suggestions if its
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
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 --set-upstream
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
6 matches
Mail list logo
