From: Frank Terbeck <ft@bewatermyfriend.org>
To: Keerthan JC <jckeerthan@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Missing options in tmux completion
Date: Tue, 15 Mar 2016 14:52:17 +0100 [thread overview]
Message-ID: <87fuvrx2zy.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <CAHyxEs0ubtu4ferbL=mrY-PYAB7uRNKBBPenwfjGexkgJDDKiQ@mail.gmail.com> (Keerthan JC's message of "Tue, 15 Mar 2016 09:36:18 -0400")
Keerthan JC wrote:
> If I look at the source of _tmux:
> https://github.com/zsh-users/zsh/blob/master/Completion/Unix/Command/_tmux#L628
> (and my local _tmux), the options start from -A.
>
> However, when I run tmux new -<Tab> I only see:
> -- option --
> -D -- in case of -A behave like attach-session's -d
> -F -- specify format of output
> -P -- print information about new session after it is created
> -c -- specify working directory for the session
> -d -- do not attach new session to current terminal
> -n -- name the initial window
> -s -- name the session
> -t -- specify target session
> -x -- specify width
> -y -- specify height
>
>
> Why are some options missing?
-A is an option to _arguments itself. I guess, we need to separate the
option lists from the options to _arguments by putting a colon in
between them. So in _tmux-new-session that would be:
_arguments -s : $args
Would make sense to do that in all helper functions in _tmux that use
_arguments. I may take a look this evening, unless someone beats me to
it.
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2016-03-15 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 13:36 Keerthan JC
2016-03-15 13:52 ` Frank Terbeck [this message]
2016-03-15 14:02 ` Keerthan JC
2016-03-15 23:42 ` 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=87fuvrx2zy.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=jckeerthan@gmail.com \
--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).