From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Ernesto Alfonso <erjoalgo@gmail.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>, git@vger.kernel.org
Subject: Re: possible completion bug with --set-upstream-to=
Date: Sat, 30 Dec 2017 09:28:06 +0100 [thread overview]
Message-ID: <20171230082806.6303-1-szeder.dev@gmail.com> (raw)
In-Reply-To: <87bmih83iu.fsf@gmail.com>
> Whenever I type the last <TAB> to complete origin/master, as in below:
>
> > git branch --set-upstream-to=orig<TAB>
>
> what I get is:
>
> > git branch origin/master
Yeah, this shouldn't happen.
> instead of the expected:
>
> > git branch --set-upstream-to=origin/master
And indeed this is the expected behavior.
> git version and OS:
>
> >git version 2.1.4
I couldn't reproduce the wrong behavior you saw using v2.1.4 in a
regular setup.
However, I could reproduce it after I removed the '=' character from
the set of characters in $COMP_WORDBREAKS, but then all completions
after an '--option=' are affected, e.g. 'pulseaudio --daemonize=t<TAB>
becomes 'pulseaudio true', too.
Could you tell us the content of your $COMP_WORDBREAKS using the
output of the following command (to make the included space, tab and
newline visible):
printf "$COMP_WORDBREAKS" |tr ' \t\n' STN ; echo
If it's indeed the case that $COMP_WORDBREAKS is missing the '=', then
you should add it back and check whether it fixed the issue. If it
did fix it, then you should try to figure out how the '=' got removed
from there. Perhaps you used a program that ships its own completion
script whose developers changed $COMP_WORDBREAKS to their liking, not
knowing about its effect on other completion scripts.
Gábor
next prev parent reply other threads:[~2017-12-30 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 0:26 possible completion bug with --set-upstream-to= Ernesto Alfonso
2017-12-30 8:28 ` SZEDER Gábor [this message]
2017-12-30 14:51 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171230082806.6303-1-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=erjoalgo@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).