git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jakob Pfender <jpfender@elegosoft.com>,
	git@vger.kernel.org, johannes.schindelin@gmx.de,
	lee.marlow@gmail.com, markus.heidelberg@web.de,
	spearce@spearce.org, bebarino@gmail.com, ted@tedpavlic.com,
	tlikonen@iki.fi, trast@student.ethz.ch
Subject: Re: [PATCH] git-completion: Add git help completion for aliases
Date: Tue, 22 Mar 2011 09:23:55 +0100	[thread overview]
Message-ID: <20110322082355.GE14520@neumann> (raw)
In-Reply-To: <7vhbawno11.fsf@alter.siamese.dyndns.org>

On Mon, Mar 21, 2011 at 02:48:10PM -0700, Junio C Hamano wrote:
> Jakob Pfender <jpfender@elegosoft.com> writes:
> 
> > Enable bash completion for "git help <alias>", analogous to "git
> > <alias>", which was already implemented.
> >
> > Signed-off-by: Jakob Pfender <jpfender@elegosoft.com>
> > ---
> >  contrib/completion/git-completion.bash |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/contrib/completion/git-completion.bash
> > b/contrib/completion/git-completion.bash
> > index 893b771..f9a74d3 100755
> > --- a/contrib/completion/git-completion.bash
> > +++ b/contrib/completion/git-completion.bash
> > @@ -1506,7 +1506,7 @@ _git_help ()
> >  		;;
> >  	esac
> >  	__git_compute_all_commands
> > -	__gitcomp "$__git_all_commands
> > +	__gitcomp "$__git_all_commands $(__git_aliases)
> >  		attributes cli core-tutorial cvs-migration
> >  		diffcore gitk glossary hooks ignore modules
> >  		repository-layout tutorial tutorial-2
> 
> This patch may not be _wrong_ per-se, but it it useful in practice?
> 
> I dunno.

I think most people use 'git help <cmd>' to bring up the man page of
given git command.  Since my aliases don't have a man page (and I
doubt that any alias will have one), I would never run 'git help
<alias>' myself, because it would only lead to a 'man page not
available' error.  Well, at least so I thought, because I never knew
that 'git help <alias>' actually prints the definition of the alias.
It's definitely shorter and easier than 'git config --get
alias.<alias>', but on the other hand it clutters 'git help <TAB>
output, especially if you have a lot of aliases.  If I had aliases
like 'ci' or 'co' instead of 'commit' and 'checkout', then I would
definitely not want to see them after 'git help <TAB>'.

So I don't know either.

Sidenote: the completion for 'git help' already lists custom git
commands (i.e. a script named 'git-<cmd>' somewhere in $PATH'), and
those are likely not documented either.

> Don't people usually use aliases so that they do not have to type long
> command names that would need completion?

I mostly use aliases for a command and a couple of options (e.g. a
custom log format), and give them meaningful names.


Best,
Gábor

  parent reply	other threads:[~2011-03-22  8:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21  9:25 [PATCH] git-completion: Add git help completion for aliases Jakob Pfender
2011-03-21 21:48 ` Junio C Hamano
2011-03-21 22:07   ` Johannes Schindelin
2011-03-22  7:53     ` Junio C Hamano
2011-03-22  8:44       ` Johannes Schindelin
2011-03-22  8:50       ` SZEDER Gábor
2011-03-22  9:16         ` Erik Faye-Lund
2011-03-22  9:18           ` Erik Faye-Lund
2011-03-22 10:09           ` SZEDER Gábor
2011-03-22 10:28             ` Erik Faye-Lund
2011-03-22 16:38               ` Michael J Gruber
2011-03-22 20:25               ` SZEDER Gábor
2011-03-23 10:32                 ` Erik Faye-Lund
2011-03-23 12:11                   ` Jakub Narebski
2011-03-23 12:16                     ` Erik Faye-Lund
2011-03-22 17:25         ` Junio C Hamano
2011-03-22 21:21           ` SZEDER Gábor
2011-03-22  8:23   ` SZEDER Gábor [this message]
2011-03-22  9:23   ` Michael J Gruber

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=20110322082355.GE14520@neumann \
    --to=szeder@ira.uka.de \
    --cc=bebarino@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=jpfender@elegosoft.com \
    --cc=lee.marlow@gmail.com \
    --cc=markus.heidelberg@web.de \
    --cc=spearce@spearce.org \
    --cc=ted@tedpavlic.com \
    --cc=tlikonen@iki.fi \
    --cc=trast@student.ethz.ch \
    /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).