git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH] completion: complete "git diff ...branc<TAB>"
Date: Thu, 24 Feb 2011 15:07:33 +0100	[thread overview]
Message-ID: <4D666625.70608@drmicha.warpmail.net> (raw)
In-Reply-To: <20110224135821.GA14720@neumann>

SZEDER Gábor venit, vidit, dixit 24.02.2011 14:58:
> On Thu, Feb 24, 2011 at 01:24:57PM +0100, Michael J Gruber wrote:
>> Reminds me fo the following: Typing
>>
>> git log origin/next@{1}..o<TAB>
>>
>> gives
>>
>> git log origin/next{1}..o
>>
>> WTF? Completion eats at babies!
> 
> Interesting, I can't seem to be able to reproduce.
> 
>   git log origin/next@{1}..o<TAB>
> 
> gives me
> 
>   git log origin/next@{1}..origin/
> 
> and a TAB after that gives me all the remote branches from origin, as
> it is supposed to, leaving the @{1} intact.
> 
> Which git, bash, and bash completion versions are you using?

git version 1.7.4.1.224.gefc87
(yesterday's next, but I've been observing this for a while now)

GNU bash, Version 4.1.7(1)-release (x86_64-redhat-linux-gnu)
(Fedora 14+updates)

git-completion from next a few days ago

(Also, I just tried with LANG=C, so it's not the de_DE locale nor utf8.)

Michael

  reply	other threads:[~2011-02-24 14:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 21:43 [PATCH] completion: complete "git diff ...branc<TAB>" Junio C Hamano
2011-02-24 12:24 ` Michael J Gruber
2011-02-24 13:58   ` SZEDER Gábor
2011-02-24 14:07     ` Michael J Gruber [this message]
2011-02-24 15:13 ` SZEDER Gábor
2011-02-24 17:09   ` Junio C Hamano
2011-03-10 18:12     ` [PATCH 1/2] bash: fix misindented esac statement in __git_complete_file() SZEDER Gábor
2011-03-10 18:12       ` [PATCH 2/2] bash: complete 'git diff ...branc<TAB>' SZEDER Gábor
2011-03-10 19:30         ` Junio C Hamano

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=4D666625.70608@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=spearce@spearce.org \
    --cc=szeder@ira.uka.de \
    /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).