From: Marko Myllynen <myllynen@redhat.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] _virsh (Was: Re: zsh virsh completion)
Date: Thu, 21 Jul 2016 15:32:14 +0300 [thread overview]
Message-ID: <6c163098-a62d-a6a4-d6a4-62894dfee8de@redhat.com> (raw)
In-Reply-To: <20160721065726.GD2467@tarsus.local2>
Hi,
On 2016-07-21 09:57, Daniel Shahaf wrote:
> Marko Myllynen wrote on Wed, Jul 20, 2016 at 11:36:36 +0300:
>> On 2016-07-20 09:58, Daniel Shahaf wrote:
>>> Marko Myllynen wrote on Mon, Jul 18, 2016 at 15:06:52 +0300:
>>>> + _cache_virsh_cmds[$_cache_virsh_cmds[(i)$icmd]]=()
>>>> + done
>>>> fi
>>>> if (( ! $+_cache_virsh_cmdopts )); then
>>>> typeset -gA _cache_virsh_cmdopts
>>>> fi
>>>> _arguments -A "-*" -C -S -s -w \
>>>
>>> Oliver remarked on the -w earlier, are you quite sure it's correct?
>>>
>>> -w In combination with -s, allow option stacking even if one
>>> or more of the options take arguments. For example, if
>>> -x takes an argument, with no -s, `-xy' is considered as
>>> a single (unhandled) option; with -s, -xy is an option
>>> with the argument `y'; with both -s and -w, -xy may be
>>> the option -x and the option -y with arguments still to
>>> come.
>>>
>>> (-s and -w are options to _arguments, -xy is a word on the command line
>>> being completed)
>>
>> I mentioned that virsh accepts all the following: -r -d 0, -r -d0, -rd
>> 0, or -rd0. So to me it would seem that -s -w is correct here, right?
>
> All these require only -s [without -w].
>
> Does virsh accept «-dr 0» where the 0 is argument to -d [regardless of
> whether -r takes an argument]? _That_'s what -w is about.
Aha, no, it doesn't - yes that sounds very rare indeed, so much that I
didn't even think of that scenario.
> Could you suggest how to clarify the man page section I quoted?
Perhaps change "with both -s and -w, -xy may be the option -x and the
option -y with arguments still to come" to "... with arguments still to
come for -x"?
Thanks,
--
Marko Myllynen
next prev parent reply other threads:[~2016-07-21 12:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 11:52 zsh virsh completion Marko Myllynen
2016-07-11 15:03 ` Roman Neuhauser
2016-07-11 16:40 ` Bart Schaefer
2016-07-11 22:07 ` Oliver Kiddle
2016-07-12 10:23 ` Marko Myllynen
2016-07-13 4:59 ` Daniel Shahaf
2016-07-18 12:06 ` Marko Myllynen
2016-07-20 6:58 ` [PATCH] _virsh (Was: Re: zsh virsh completion) Daniel Shahaf
2016-07-20 8:36 ` Marko Myllynen
2016-07-21 6:57 ` Daniel Shahaf
2016-07-21 12:32 ` Marko Myllynen [this message]
2016-07-22 6:30 ` Daniel Shahaf
2016-07-22 8:17 ` Marko Myllynen
2016-07-21 16:12 ` Oliver Kiddle
2016-07-21 16:19 ` Marko Myllynen
2016-07-22 7:19 ` Daniel Shahaf
2016-08-31 21:15 ` Oliver Kiddle
2016-09-02 5:23 ` Daniel Shahaf
2016-09-02 15:02 ` Oliver Kiddle
2016-09-04 4:01 ` Daniel Shahaf
2016-09-07 6:39 ` Bart Schaefer
2016-09-09 22:09 ` Oliver Kiddle
2016-09-11 9:08 ` Daniel Shahaf
2016-09-14 23:19 ` Oliver Kiddle
2016-09-04 21:24 ` Daniel Shahaf
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=6c163098-a62d-a6a4-d6a4-62894dfee8de@redhat.com \
--to=myllynen@redhat.com \
--cc=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).