From: Nikolai Weibull <now@bitwi.se>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: Mikael Magnusson <mikachu@gmail.com>, Zsh Workers <zsh-workers@zsh.org>
Subject: Re: Git commands or aliases first?
Date: Fri, 22 Jul 2011 14:40:36 +0200 [thread overview]
Message-ID: <CADdV=Ms=a=teDp+nG1poyfYaMK6GuutHR4F__-9uhLD75ES79Q@mail.gmail.com> (raw)
In-Reply-To: <87aac6jz8n.fsf@ft.bewatermyfriend.org>
On Fri, Jul 22, 2011 at 14:06, Frank Terbeck <ft@bewatermyfriend.org> wrote:
> Mikael Magnusson wrote:
>> On 22 July 2011 13:40, Nikolai Weibull <now@bitwi.se> wrote:
>>> Hi!
>>>
>>> What is the desired tag order for Git commands and aliases?
>>>
>>> My conclusion is that the current behavior is incorrect. My reasoning
>>> is that git will prefer invoking a command over an alias with the same
>>> name.
>>>
>>> Does anyone have a contradictory opinion, or should I merge this change?
>>
>> We could show aliases first, but leave out ones that are also
>> commands? On the one hand, I would want to complete my aliases before
>> the commands, on the other hand I usually make alias names short
>> enough to not need completing. On the third hand it's configurable
>> with group-order anyway, so either is fine with me :). Ie
>> zstyle ':completion:*:git:*' group-order main-porcelain-commands
>
> If there is a git alias "add", git will still use the command, not the
> alias. So that would make sense.
>
> I also think aliases should be completed before commands, since that
> will probably be "commands" the user calls regularly.
OK, I’ve implemented it this way now.
prev parent reply other threads:[~2011-07-22 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 11:40 Nikolai Weibull
2011-07-22 11:58 ` Mikael Magnusson
2011-07-22 12:04 ` Nikolai Weibull
2011-07-22 12:06 ` Frank Terbeck
2011-07-22 12:40 ` Nikolai Weibull [this message]
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='CADdV=Ms=a=teDp+nG1poyfYaMK6GuutHR4F__-9uhLD75ES79Q@mail.gmail.com' \
--to=now@bitwi.se \
--cc=ft@bewatermyfriend.org \
--cc=mikachu@gmail.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).