From: Jakub Narebski <jnareb@gmail•com>
To: "Shawn O. Pearce" <spearce@spearce•org>
Cc: Junio C Hamano <junkio@cox•net>, git@vger•kernel.org
Subject: Re: [PATCH 1/8] bash: Remove short option completions for branch/checkout/diff.
Date: Mon, 5 Feb 2007 10:16:16 +0100 [thread overview]
Message-ID: <200702051016.16785.jnareb@gmail.com> (raw)
In-Reply-To: <20070205024704.GB12917@spearce.org>
Shawn O. Pearce wrote:
> Completing single character options is rather useless in my mind.
> The bash completion is always out of date with respect to the
> actual set of supported options, and by definition they are a
> single character. Hitting '-<tab><tab>' to identify the list of
> supported options gives *no* detail about what the options do,
> and I still have to enter the option letter to complete it.
>
> Completing `git am --w<tab>hitespace=s<tab>trip ` with just 6
> keystrokes on the other hand is very informative (whitespace,
> strip!) and saves many keystrokes. That's why long options are
> supported, for at least the more commonly accessed ones.
It would be nice to have long option for each git command single
character (short) option, for example --patch as long option to
git-diff-tree -p option, etc.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-02-05 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 7:38 [PATCH 1/8] bash: Remove short option completions for branch/checkout/diff Shawn O. Pearce
2007-02-04 10:27 ` Jakub Narebski
2007-02-04 10:49 ` Junio C Hamano
2007-02-05 2:47 ` Shawn O. Pearce
2007-02-05 9:16 ` Jakub Narebski [this message]
2007-02-05 9:19 ` Shawn O. 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=200702051016.16785.jnareb@gmail.com \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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