From: Mikael Magnusson <mikachu@gmail.com>
To: gi1242+zsh@gmail.com, zsh-workers@zsh.org
Subject: Re: _arguments: Sets not working?
Date: Sun, 23 Jan 2011 19:51:25 +0100 [thread overview]
Message-ID: <AANLkTinifNrj_M7ycR06y9cpawy5nJdyBpY30XvcsUc0@mail.gmail.com> (raw)
In-Reply-To: <20110123174508.GC2593@andrew.cmu.edu>
On 23 January 2011 18:45, <gi1242+zsh@gmail.com> wrote:
> Hi All,
>
> It looks like argument sets separated by single hyphens are not working.
> You can see the bug by trying to complete arguments of 'vncserver'. When
> you ask for completions, none are returned. [Behaviour persists in
> latest release from Git]
>
> The vncserver code seems to use completion sets. From zshcomsys, line
> 3397 in zsh4.3.10:
>
> It is possible to specify multiple sets of options and arguments
> with the sets separated by single hyphens. The specifications before
> the first hyphen (if any) are shared by all the remaining sets.
>
> (I couldn't get the documentation from git to build on my system, so
> don't know if the behaviour has changed or not.)
>
> When I remove lines
>
> - start \
> - kill \
> - help \
>
> from Completion/**/_vnc, then options are completed as expected. With
> the above lines, I get no argument completions; and I can't figure out
> how the syntax contradicts the man page. Is there a bug?
>
> Thanks,
>
> GI
FWIW, the completion appears to work fine here. If i specify -help, no
other completions are offered, and same for -kill or the other set as
well. I even found i still had an Xvnc process running from a few
weeks ago when i pressed tab again after -kill :).
--
Mikael Magnusson
next prev parent reply other threads:[~2011-01-23 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 17:45 gi1242+zsh
2011-01-23 18:48 ` Peter Stephenson
2011-01-23 18:51 ` Mikael Magnusson [this message]
2011-01-23 20:37 ` gi1242+zsh
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=AANLkTinifNrj_M7ycR06y9cpawy5nJdyBpY30XvcsUc0@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=gi1242+zsh@gmail.com \
--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).