From: "Yin Ping" <pkufranky@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Jeff King" <peff@peff.net>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Jari Aalto" <jari.aalto@cante.net>,
git@vger.kernel.org
Subject: Re: [PATCH] On error, do not list all commands, but point to --help option.
Date: Sun, 21 Oct 2007 14:33:26 +0800 [thread overview]
Message-ID: <46dff0320710202333g70b022f4r6574e93aa0463065@mail.gmail.com> (raw)
In-Reply-To: <20071021032953.GC14735@spearce.org>
On 10/21/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> Jeff King <peff@peff.net> wrote:
> > On Sat, Oct 20, 2007 at 10:06:53PM -0400, Shawn O. Pearce wrote:
> >
> > > I actually had to do `git config alias.upsh push` just to keep
> > > myself from screaming every time I made a small typo and Git gave
> > > me a screenful of "helpful reminders".
> >
> > Yeah, somebody should really work on bash completion...
>
> $ git pu<TAB><TAB>
> pull push
>
> By the time I type out "pus" and hit tab I've already typed out
> the name "push ". Except I frequently find myself getting the
> u before the p, which can't complete. Of course with the above
> alias in place "git u<TAB>" completes out uniquely to "git push "
> (between bash completion and the alias expansion).
>
> But that alias isn't there for my bash tab completion. Its there
> exactly because otherwise "git upsh" gives me 31 lines of useless
> (to me) output without it.
>
My way to resolve this is to define some alias begenning with 'gt' for
frequently used commands, such as 'gtps -> git-push, gtpl ->
git-pull, gtco->git-checkout, gtci->git-commit, gtbr->git-branch'.
so that when i type 'gt<TAB>', only commands that i frequently use are
listed.
--
franky
next prev parent reply other threads:[~2007-10-21 6:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 8:24 [PATCH] On error, do not list all commands, but point to --help option Jari Aalto
2007-10-20 20:28 ` Johannes Schindelin
2007-10-20 22:28 ` Jari Aalto
2007-10-20 23:02 ` Johannes Schindelin
2007-10-21 2:06 ` Shawn O. Pearce
2007-10-21 3:24 ` Jeff King
2007-10-21 3:29 ` Shawn O. Pearce
2007-10-21 6:33 ` Yin Ping [this message]
2007-10-21 8:58 ` Wincent Colaiuta
2007-10-21 12:42 ` Andreas Ericsson
2007-10-21 13:13 ` Jan Hudec
2007-10-21 14:17 ` Andreas Ericsson
2007-10-24 0:28 ` Salikh Zakirov
2007-10-20 22:41 ` Jari Aalto
2007-10-21 3:33 ` Shawn O. Pearce
2007-10-21 10:09 ` Jan Hudec
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=46dff0320710202333g70b022f4r6574e93aa0463065@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
--cc=peff@peff.net \
--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).