From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder@ira.uka.de>,
"Junio C Hamano" <gitster@pobox.com>,
"Thomas Rast" <trast@student.ethz.ch>
Subject: Re: [PATCH] completion: fix issues with COMP_WORDBREAKS
Date: Mon, 16 Apr 2012 13:44:58 +0300 [thread overview]
Message-ID: <CAMP44s3cM5nZnN6W6KCw-aVdT_-Ax1YTopHkR6b0msSsHhQDmA@mail.gmail.com> (raw)
In-Reply-To: <20120416003850.GH5813@burratino>
On Mon, Apr 16, 2012 at 3:38 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Felipe Contreras wrote:
>
>> In fact if COMP_WORDBREAKS doesn't contain a colon the completion gets
>> all messed up. For example:
>>
>> git push origin master:<TAB>
>> git diff master:<TAB>
>>
>> The "master:" prefix would be added again, unnecessarily.
>
> Thanks. Yeah, that sounds broken.
>
> Unfortunately the patch introduces a regression: if after loading the
> completion script I set COMP_WORDBREAKS not to contain a colon, then
> with the current completion script
>
> git show HEAD:Docu<TAB>
>
> completes fine, but with the patched completion script it seems to
> get confused and strips off the HEAD.
I don't understand, I tested this and it was working fine, but not any more =/
Maybe I was testing on zsh.
I guess this should be dropped then.
Cheers.
--
Felipe Contreras
prev parent reply other threads:[~2012-04-16 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 21:17 [PATCH] completion: fix issues with COMP_WORDBREAKS Felipe Contreras
2012-04-16 0:38 ` Jonathan Nieder
2012-04-16 10:44 ` Felipe Contreras [this message]
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=CAMP44s3cM5nZnN6W6KCw-aVdT_-Ax1YTopHkR6b0msSsHhQDmA@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=szeder@ira.uka.de \
--cc=trast@student.ethz.ch \
/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).