On Tue, May 10, 2011 at 10:47:49PM +0200, Sverre Rabbelier wrote: > On Tue, May 10, 2011 at 22:39, Jeff King <peff@xxxxxxxx> wrote: > > Hrm. That code doesn't appear in our completion at all. We provide our > > own _get_comp_words_by_ref, but if it is already defined, we use > > whatever is there. So on my box, the problematic code comes from > > /etc/bash_completion. And I think it is a bug there, as this is one of > > the first things called (so git's completion hasn't had a change to > > introduce any bugs yet :) ). > > Most curious, since it doesn't happen when I don't source git > completion. Perhaps it'll happen for any completion, or maybe we're > using the completion wrong somehow? I'm on Debian wheezy/sid. Right. Bash calls into our __git() completion function, which calls the implementation of _get_comp_words_by_ref from /etc/bash_completion, which has the bug. If you don't source git completion, then you are just getting bash's default file completion. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html