From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org
Subject: Re: git-browse-help?
Date: Sat, 15 Dec 2007 06:11:54 -0500 [thread overview]
Message-ID: <20071215111154.GB3447@coredump.intra.peff.net> (raw)
In-Reply-To: <20071215110153.GA3447@coredump.intra.peff.net>
On Sat, Dec 15, 2007 at 06:01:53AM -0500, Jeff King wrote:
> problem. Shawn, perhaps it should simply ignore *--* as plumbing?
And here is a patch to do that.
-- >8 --
teach bash completion to treat commands with "--" as plumbing
There is a convention that commands containing a double-dash
are implementation details and not to be used by mortals. We
should automatically remove them from the completion
suggestions as plumbing.
Signed-off-by: Jeff King <peff@peff.net>
---
BTW, Junio, I remember discussion a long time ago about doing:
cover letter
-- >8 --
commit
---
diff
versus
commit
---
cover letter
diff
and I recall that you did not have a strong preference. I have started
using the former, as I find it a bit more convenient to write (and I
think it is more readable when you are following up a discussion rather
than writing a real cover letter or commenting on the patch). However,
I wanted to confirm that you don't find it significantly more annoying.
contrib/completion/git-completion.bash | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index 58e0e53..2fd32db 100755
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -291,7 +291,7 @@ __git_commands ()
for i in $(git help -a|egrep '^ ')
do
case $i in
- add--interactive) : plumbing;;
+ *--*) : plumbing pattern;;
applymbox) : ask gittus;;
applypatch) : ask gittus;;
archimport) : import;;
@@ -308,7 +308,6 @@ __git_commands ()
diff-tree) : plumbing;;
fast-import) : import;;
fsck-objects) : plumbing;;
- fetch--tool) : plumbing;;
fetch-pack) : plumbing;;
fmt-merge-msg) : plumbing;;
for-each-ref) : plumbing;;
--
1.5.4.rc0.1124.g1b66f-dirty
next prev parent reply other threads:[~2007-12-15 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 9:28 git-browse-help? Jeff King
2007-12-14 17:38 ` git-browse-help? Junio C Hamano
2007-12-15 10:08 ` git-browse-help? Jeff King
2007-12-15 11:01 ` git-browse-help? Jeff King
2007-12-15 11:11 ` Jeff King [this message]
2007-12-15 19:25 ` git-browse-help? Junio C Hamano
2007-12-15 22:25 ` git-browse-help? Shawn O. Pearce
2007-12-15 19:26 ` git-browse-help? Junio C Hamano
2007-12-16 7:21 ` git-browse-help? Jeff King
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=20071215111154.GB3447@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).