Re: Calling all bash completion experts..

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Sat, 25 Nov 2006, Shawn Pearce wrote:
> 
> I added the nospace option because of the completion for fetch/push,
> cat-file, diff-tree and ls-tree.
> 
> The problem is the file completion for e.g. cat-file.  We don't
> want a space added after we complete a directory name, so you can
> complete further, e.g.:
> 
>   git cat-file -p ma<tab>con<tab>comp<tab>git-com<tab>

But that's how directory completion _always_ works. Completion doesn't add 
spaces to directories anyway, it adds a "/".

The branch-name thing is well-taken: you don't want to add a space after a 
branch-name, although neither do you want to add a ":" by default.

So "nospace" after a branch (or tag) name sounds sane, but nowhere else 
that I can see.

		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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]