git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: fREW Schmidt <frioux@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "SZEDER Gábor" <szeder@ira.uka.de>,
	"Rolf Leggewie" <foss@rolf.leggewie.biz>,
	git@vger.kernel.org
Subject: Re: broken bash completion
Date: Sat, 5 May 2012 08:57:46 -0500	[thread overview]
Message-ID: <CADVrmKRjw6VFQAnQruBmc1OhOaswpOtzb+E8G_KooYiz6SuStA@mail.gmail.com> (raw)
In-Reply-To: <CAMP44s0q_zeVwzhgeda1=9+Psjr5PaO1QtHT1QC0RwyCpfd=rg@mail.gmail.com>

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.

--
fREW Schmidt
http://blog.afoolishmanifesto.com

  reply	other threads:[~2012-05-05 13:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 14:09 broken bash completion Rolf Leggewie
2012-05-04 23:32 ` SZEDER Gábor
2012-05-05  4:24   ` Rolf Leggewie
2012-05-05 12:13     ` SZEDER Gábor
2012-05-05 12:22       ` Andreas Schwab
2012-05-05 13:11       ` Felipe Contreras
2012-05-05 13:57         ` fREW Schmidt [this message]
2012-05-05 14:26           ` Felipe Contreras

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=CADVrmKRjw6VFQAnQruBmc1OhOaswpOtzb+E8G_KooYiz6SuStA@mail.gmail.com \
    --to=frioux@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=foss@rolf.leggewie.biz \
    --cc=git@vger.kernel.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).