From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: [PATCH] _tmux: Correct completions of new-window, split-window, respawn-window, respawn-pane.
Date: Thu, 3 Aug 2017 22:37:41 +0000 [thread overview]
Message-ID: <20170803223741.17002-1-danielsh@tarpaulin.shahaf.local2> (raw)
This follows up to 41467 which patched new-session.
---
Completion/Unix/Command/_tmux | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Completion/Unix/Command/_tmux b/Completion/Unix/Command/_tmux
index 5f5bea922..7ef20c666 100644
--- a/Completion/Unix/Command/_tmux
+++ b/Completion/Unix/Command/_tmux
@@ -540,7 +540,7 @@ _tmux-new-window() {
'-n+[specify a window name]:window name' \
'-P[print information about new window after it is created]' \
'-t+[specify target window]:window:__tmux-windows' \
- '*:: :_cmdstring'
+ '*:: :_cmdambivalent'
}
_tmux-next-layout() {
@@ -628,7 +628,7 @@ _tmux-respawn-pane() {
_arguments -s -A "-*" -S \
'-k[kill window if it is in use]' \
'-t+[specify target pane]:pane:__tmux-pane' \
- ':command:_cmdstring'
+ ':command:_cmdambivalent'
}
_tmux-respawn-window() {
@@ -636,7 +636,7 @@ _tmux-respawn-window() {
_arguments -s -A "-*" -S \
'-k[kill window if it is in use]' \
'-t+[specify target window]:window:__tmux-windows' \
- ':command:_cmdstring'
+ ':command:_cmdambivalent'
}
_tmux-rotate-window() {
@@ -855,7 +855,7 @@ _tmux-split-window() {
"-l[define new pane's size]:size" \
"-p[define new pane's size in percent]:size (percentage)" \
'-t+[specify target pane]:pane:__tmux-panes' \
- ':command:_cmdstring'
+ ':command:_cmdambivalent'
# Yes, __tmux-panes is correct here. The behaviour was changed
# in recent tmux versions and makes more sense. Except that
# changing the command's name might annoy users. So it stays like
The behaviour is documented in tmux(1):
Additionally, the new-window, new-session, split-window, respawn-window
and respawn-pane commands allow shell-command to be given as multiple
arguments and executed directly (without ‘sh -c’).
Cheers,
Daniel
reply other threads:[~2017-08-03 22:37 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=20170803223741.17002-1-danielsh@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--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).