From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jakob Pfender <jpfender@elegosoft.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
<git@vger.kernel.org>, <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 22:21:31 +0100 [thread overview]
Message-ID: <20110322212131.GB30604@neumann> (raw)
In-Reply-To: <7vsjufkqxl.fsf@alter.siamese.dyndns.org>
On Tue, Mar 22, 2011 at 10:25:58AM -0700, Junio C Hamano wrote:
> SZEDER Gábor <szeder@ira.uka.de> writes:
>
> > I think this is not necessary. We already run __git_aliases() every
> > time after 'git <TAB>', and it was not an issue so far.
>
> If we allow that line of reasoning, the cached $__git_all_commands that
> can go stale needs to be removed, no? I think folks running bash on
> windows wanted it and it would be helping them.
Well, Shawn wrote that it was your request ;)
http://thread.gmane.org/gmane.comp.version-control.git/32444
http://thread.gmane.org/gmane.comp.version-control.git/32438
But there was indeed a remark shortly before that about bad fork-exec
performance under Cygwin on an other topic.
> One valid looking argument against caching aliases but still caching
> commands is that the former could change on the end user's whim while the
> latter is more or less stable across releases,
Agreed.
> but people can throw their
> own "git-frotz" in their path and run it as "git frotz"
Also agreed, and been annoyed by it not being recognized
automatically. In fact I've even tried to make the completion script
detect user's commands on the fly but still without that huge loop
over the 'git help -a' output in __git_list_porcelain_commands(), but
couldn't come up with anything acceptable so far. And simply
re-sourcing the completion script is not all that difficult, which
will also take care of refreshing cached aliases, so...
> so that is not
> entirely a valid argument, either.
agreed here, too.
Best,
Gábor
next prev parent reply other threads:[~2011-03-22 21:21 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 [this message]
2011-03-22 8:23 ` SZEDER Gábor
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=20110322212131.GB30604@neumann \
--to=szeder@ira.uka.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).