From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Sat, 05 May 2012 14:26:18 GMT
Subject: Re: broken bash completion
Message-ID: <CAMP44s0HtcO0S-Vjq=XkiB7VLZq-LWr2tf2MF_HMpj=1C=LKSQ@mail.gmail.com>
In-Reply-To: <CADVrmKRjw6VFQAnQruBmc1OhOaswpOtzb+E8G_KooYiz6SuStA@mail.gmail.com>

On Sat, May 5, 2012 at 3:57 PM, fREW Schmidt <frioux@gmail.com> wrote:
> On Sat, May 5, 2012 at 8:11 AM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>>
>> On Sat, May 5, 2012 at 2:13 PM, SZEDER Gábor <szeder@ira.uka.de> wrote:
>>
>> The reason I started to use the bash completion in zsh is that the zsh
>> completion goes for 100% correctness, that means 'git checkout <TAB>'
>> took literally *minutes* in my machine on the Linux kernel repo. The
>> zsh developers said that was OK, and my patch to solve the problem was
>> not, because it would make the result less than 100% correct.
>
> Could you elaborate on how you did that?  I'm suffering from the same
> thing and don't see an obvious way to use bash-completion in zsh.

Just source the bash script:
http://git.kernel.org/?p=git/git.git;a=blob;f=contrib/completion/git-completion.bash

Alternatively you can use my wrapper that works better than zsh's bash
completion[1], but you still need the bash script anyway.

Cheers.

[1] https://github.com/felipec/git-zsh/blob/master/git-completion.zsh

-- 
Felipe Contreras