From: Rolf Leggewie Date: Wed, 02 May 2012 14:09:26 GMT Subject: broken bash completion Message-ID: <4FA14016.8050503@rolf.leggewie.biz> forward from http://code.google.com/p/git-core/issues/detail?id=11 and https://bugs.launchpad.net/bugs/853081 Hello, not sure you guys pay much attention to the issue tracker over on code.google.com so I'll try my luck here. Current bash completion works the following way. 1) only tag-completion possible: complete tag as much as possible 2) only file/dir-completion possible: complete path as much as possible 3) all of tag/file/dir-completion possible: complete tag (!) as much as possible 1 and 2 are fine, but for #3 git should really stop at the lowest common denominator for all of tags, files and directories. This is explained better in above tickets, but I'll also include an example here for illustration. Let's say I had tags debian/1.4.9-1 and debian/1.4.9-2 as well as debian/changelog file (as is common when using git-buildpackage, this is a real life example). Current bash-completion behavior for "git log debiTAB" is to complete to "git log debian/1.4.9-" when it really should be "git log debian/". Thank you for your attention. Regards Rolf