From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@zsh.org
Cc: Nikolai Weibull <now@bitwi.se>
Subject: PATCH: _git: support for user-specific sub commands
Date: Thu, 4 Mar 2010 16:45:16 +0100 [thread overview]
Message-ID: <1267717516-10175-1-git-send-email-ft@bewatermyfriend.org> (raw)
Someone asked for this on IRC.
Documentation included on top of the _git file. This also changes one
':completion:${curcontext}:' to ":completion:${curcontext}:" (single
versus double quotes), which I believe is right.
Would you agree, Nikolai?
Regards, Frank
---
Completion/Unix/Command/_git | 25 ++++++++++++++++++++++++-
1 files changed, 24 insertions(+), 1 deletions(-)
diff --git a/Completion/Unix/Command/_git b/Completion/Unix/Command/_git
index c87593e..d7570cc 100644
--- a/Completion/Unix/Command/_git
+++ b/Completion/Unix/Command/_git
@@ -1,5 +1,25 @@
#compdef git git-cvsserver git-receive-pack git-upload-archive git-upload-pack git-shell
+# Some parts of this completion's behaviour are configurable:
+#
+# Say, you got your own git sub-commands (git will run a program `git-foo'
+# when you run "git foo") and you want "git f<tab>" to complete that sub
+# commands name for you. You can make that sub-command know to the completion
+# via the user-command style:
+#
+# % zstyle ':completion:*:*:git:*' user-commands foo:'description for foo'
+#
+# `user-commands' is a list style, so you can add any number of programs there.
+# The :description part is optional, so you could add all git-* programs from
+# your $path like this:
+#
+# % zstyle ':completion:*:*:git:*' user-commands ${${(M)${(k)commands}:#git-*}/git-/}
+#
+# You could even create a function _git-foo() to handle specific completion
+# for that command.
+
+# TODO: There is still undocumented configurability in here.
+
# TODO: All if (( words[(I)-option] )) should be turned into
# if (( words[(I)-option] > 0 && words[(I)-option] < CURRENT )), as the user
# may go back and want to add an option before -option and in that case should
@@ -304,7 +324,9 @@ _git_commands () {
'upload-pack:command invoked by clone-pack and fetch-pack')
local wanted_commands
- zstyle -s ':completion:${curcontext}:' commands wanted_commands || wanted_commands="all -internal"
+ zstyle -s ":completion:${curcontext}:" commands wanted_commands || wanted_commands="all -internal"
+ local -a user_commands
+ zstyle -a ":completion:${curcontext}:" user-commands user_commands || user_commands=()
local -aU unique_wanted_commands
unique_wanted_commands=($=wanted_commands)
@@ -339,6 +361,7 @@ _git_commands () {
commands+=($internal_commands) ;;
esac
done
+ commands+=( $user_commands )
_describe -t commands 'git command' commands && ret=0
}
--
1.7.0
next reply other threads:[~2010-03-04 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 15:45 Frank Terbeck [this message]
2010-03-04 15:52 ` Nikolai Weibull
2010-03-04 16:20 ` Frank Terbeck
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=1267717516-10175-1-git-send-email-ft@bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=now@bitwi.se \
--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).