On Tue, May 10, 2011 at 11:02:53PM +0200, Sverre Rabbelier wrote: > On Tue, May 10, 2011 at 23:01, Jeff King <peff@xxxxxxxx> wrote: > > 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. > > So should we file this bug with bash's completion people? Probably, but it would be nice to reduce it to a smaller test case (or one that happens just with completions shipped by Debian) just to rule out anything git is doing. > Also, how did you manage to reproduce? It doesn't happen all the time > for me. Initially, with: $ git init repo && cd repo $ echo content >file && git add file $ git commit -am foo $ <C-R>git commit -am f<Tab> but I also get it with just: $ cd /anywhere ;# do not have to even be in a git repo $ <C-R>git<Tab> -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