From: Linus Torvalds <torvalds@osdl.org>
To: Shawn Pearce <spearce@spearce.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Calling all bash completion experts..
Date: Sat, 25 Nov 2006 11:08:28 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0611251106250.6991@woody.osdl.org> (raw)
In-Reply-To: <20061125071351.GE4528@spearce.org>
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.
next prev parent reply other threads:[~2006-11-25 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 17:45 Calling all bash completion experts Linus Torvalds
2006-11-25 7:13 ` Shawn Pearce
2006-11-25 19:08 ` Linus Torvalds [this message]
2006-11-26 4:03 ` Shawn Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0611251106250.6991@woody.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).