From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh workers <zsh-workers@zsh.org>
Subject: PATCH: update tmux completion for 2.3
Date: Wed, 09 Nov 2016 13:55:15 +0100 [thread overview]
Message-ID: <75624.1478696115@hydra.kiddle.eu> (raw)
This only covers differences that are apparent from changes in the
output of tmux list-commands. Also fixed a few typos in comments.
Oliver
diff --git a/Completion/Unix/Command/_tmux b/Completion/Unix/Command/_tmux
index 1adb7da..5679d78 100644
--- a/Completion/Unix/Command/_tmux
+++ b/Completion/Unix/Command/_tmux
@@ -153,12 +153,12 @@ _tmux_aliasmap=(
# Another thing, the description generation needs, is handling of
# $tmux_describe: If that parameter is non-empty, the sub-command function
# should only print a description of the sub-command it handles and return
-# immidiately after doing so.
+# immediately after doing so.
#
# To add support for a new sub-command, you only have to add a new
# _tmux-<foo>() function below (preferably alphabetically sorted), that
# behaves like described above; and add a alias->command pair in the
-# _tmux_aliasmap associative array above (if the comand in fact has an
+# _tmux_aliasmap associative array above (if the command in fact has an
# alias). The rest should just work[tm].
_tmux-attach-session() {
@@ -179,6 +179,7 @@ _tmux-bind-key() {
'-n[make the binding work without the need for the prefix key]' \
'-r[the key may repeat]' \
'-t+[specify mode table for the binding]:mode table:__tmux-mode-tables' \
+ '-R+[specify repeat count]:repeat count' \
'-T+[specify key table for the binding]:key table' \
'1:key' \
'*:::template:_tmux'
@@ -427,8 +428,8 @@ _tmux-list-clients() {
}
_tmux-list-commands() {
- [[ -n ${tmux_describe} ]] && print "list supported sub-commands" && return
- __tmux-nothing-else
+ [[ -n ${tmux_describe} ]] && print "list supported sub-commands" && return
+ _arguments '-F+[specify format]:format'
}
_tmux-list-keys() {
@@ -837,8 +838,10 @@ _tmux-show-window-options() {
}
_tmux-source-file() {
- [[ -n ${tmux_describe} ]] && print "execute tmux commands from a file" && return
- _files
+ [[ -n ${tmux_describe} ]] && print "execute tmux commands from a file" && return
+ _arguments \
+ "-q[don't report error if path doesn't exist]" \
+ '*:path:_directories'
}
_tmux-split-window() {
@@ -939,7 +942,7 @@ _tmux-wait-for() {
}
# --- Utility functions ---
-# They should be called __tmux-*() and kept seperate from the
+# They should be called __tmux-*() and kept separate from the
# sub-command functions.
function __tmux-attributes() {
@@ -1119,7 +1122,7 @@ function __tmux-option-guard() {
'window-status-separator:MSG:separator string'
'window-status-style:__tmux-style'
'window-style:__tmux-style'
- 'wrap-seach:DESC:on off'
+ 'wrap-search:DESC:on off'
'xterm-keys:DESC:on off'
)
fi
reply other threads:[~2016-11-09 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=75624.1478696115@hydra.kiddle.eu \
--to=okiddle@yahoo.co.uk \
--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).