zsh-users
 help / color / mirror / code / Atom feed
From: "Benjamin R. Haskell" <zsh@benizi.com>
To: Sebastian Stark <seb-zsh@biskalar.de>
Cc: Conrad Irwin <conrad.irwin@gmail.com>, zsh-users@zsh.org
Subject: Re: _git Completion and custom commands
Date: Tue, 28 Sep 2010 02:30:38 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.01.1009280219410.19964@hp> (raw)
In-Reply-To: <D49502D2-C34A-43B8-8FD5-D3D3A52342B0@biskalar.de>

On Tue, 28 Sep 2010, Sebastian Stark wrote:

>
> Am 28.09.2010 um 06:06 schrieb Benjamin R. Haskell:
>>> My question is then: how would I add my custom commands' names to 
>>> the list already completed by _git (without completely overriding or 
>>> modifying the system-wide configuration)?
>>
>> This has bothered me for a while, too.  I think _git should include 
>> these by default.  But, it's pretty easy to add:
>>
>> zstyle ':completion:*:git:*' user-commands ${${(k)commands[(I)git-*]}#git-}
>>
>> (I've found _git to be very about what it allows you to override via zstyles)

                               ^ (very good about)

>>
>> Explanation of the '${${(k)commands[(I)git-*]}#git-}' portion:
>>
>> $commands is a built-in associative array that maps basenames to 
>> their full paths.
>>
>> E.g. one of my custom git- commands that it picks up is:
>> commands[git-build-zsh]=/home/bhaskell/bin/git-build-zsh
>>
>> So, we're looking for the keys '(k)'.  And we only want entries in 
>> the hash that have (I)ndexes matching 'git-*'.  Then we want to 
>> remove the leading 'git-' portion ( ${...#git-} ).
>
> All this is just because then you can type "git bu<TAB>" instead of 
> "git-bu<TAB>"?

Roughly, yes.  But "all this" is really just adding a line to a startup 
file.  The rest was just over-explanation (since the OP mentioned just 
switching from bash).


> Or is there more to it? Perhaps I do not understand.

If you started learning git before all the git-cmd -style commands were 
no longer in path, maybe that git-bu<tab> seems natural, but I don't 
like that style at all.  And personally, typing 'git ' is becoming so 
common I may alias it to 'g '.

The other portion not mentioned is that commands thus added show up in 
the normal list:

git <tab>

produces lots of output, but ends with my custom commands all grouped at 
the end.

-- 
Best,
Ben


  reply	other threads:[~2010-09-28  6:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28  0:29 Conrad Irwin
2010-09-28  4:06 ` Benjamin R. Haskell
2010-09-28  5:28   ` Sebastian Stark
2010-09-28  6:30     ` Benjamin R. Haskell [this message]
2010-09-28  8:03   ` Frank Terbeck
2010-09-28 18:01     ` Conrad Irwin

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=alpine.LNX.2.01.1009280219410.19964@hp \
    --to=zsh@benizi.com \
    --cc=conrad.irwin@gmail.com \
    --cc=seb-zsh@biskalar.de \
    --cc=zsh-users@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).