So, I'm a happy but clueless user of the bash completion, and one thing drives me wild: when it has found an exclusive completion, it doesn't add the final space at the end, but just beeps at you when you <tab> again. So I do "git repa<tab>" and get "git repack", which is fine, but I really _wanted_ to get "git repack " (with the space at the end), since I've now got a unique command, and that's the normal completion behaviour (ie I want it to act the same way that "git-repa<tab>" would have acted). The same is true of filename arguments, btw: git commit cont<tab>com<tab><tab> gives me git commit contrib/completion/git-completion.bash but again, it doesn't seem to do the right thing about the fact that it was the unique choice, so it didn't add the final space, and when you press <tab> more to get what the other choices are, it doesn't show you any other choices (because there are none). Now, without knowing the completion syntax, I assume it's the "-o nospace" things in the completion file. So I'm wondering _why_ that "nospace" is there, and whether this could be fixed? Linus - 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