From: Marko Myllynen <myllynen@redhat.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>, zsh-workers@zsh.org
Subject: Re: _libvirt, $opt_args, and noglob
Date: Wed, 7 Sep 2016 12:53:13 +0300 [thread overview]
Message-ID: <23031e84-df6c-90c7-b5c0-9d6eb157dd61@redhat.com> (raw)
In-Reply-To: <20160906234646.GB17896@fujitsu.shahaf.local2>
Hi,
On 2016-09-07 02:46, Daniel Shahaf wrote:
> Daniel Shahaf wrote on Sun, Sep 04, 2016 at 18:26:22 +0000:
>> In the special case of _libvirt, simply adding noglob to the
>> _call_program arguments would probably fix this.
>
> Done, but the last line touches the sudo invocation from Oliver's
> gain-privileges patch. Oliver: shall I wait with committing this until
> you've committed gain-privileges?
>
> @@ -224,7 +224,7 @@ case $state in
> local srv ; (( ${(k)words[(I)--server]} > 0 )) && srv=${words[1+${(k)words[(I)--server]}]}
> [[ -z $srv ]] && return 1
> [[ -n ${srv//[[:alnum:]]} ]] && return 1
> - _wanted clients expl client compadd ${=${${(f):-"$(sudo virt-admin ${(Q)conn_opt} srv-clients-list --server $srv 2>/dev/null)"}/ [a-z]*}//[^0-9]} && return 0
> + _wanted clients expl client compadd ${=${${(f):-"$(noglob sudo virt-admin ${(Q)conn_opt} srv-clients-list --server $srv 2>/dev/null)"}/ [a-z]*}//[^0-9]} && return 0
> fi
> [[ -z $_cache_virt_admin_cmd_opts[$cmd] ]] && \
> _cache_virt_admin_cmd_opts[$cmd]=${(M)${${${${=${(f)"$(_call_program virt-admin virt-admin help $cmd 2>&1)"}}/\[}/\]}/\;}:#-[-0-9A-Za-z]*}
> ]]]
Do we need any of (Q)'s there any more after your addition of:
uri=${uri//(#m)\\([\\:])/${MATCH[2]}} # opt_args elements are colon-escaped
Based on a quick test looks like they could be dropped (or
perhaps even changed to (q))?
Thanks,
--
Marko Myllynen
next prev parent reply other threads:[~2016-09-07 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 18:26 Daniel Shahaf
2016-09-06 23:46 ` Daniel Shahaf
2016-09-07 9:53 ` Marko Myllynen [this message]
2016-09-07 22:42 ` 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=23031e84-df6c-90c7-b5c0-9d6eb157dd61@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).