From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: zsh-users@zsh.org
Subject: Re: device cannot be completed after "ip link show dev"
Date: Thu, 2 Apr 2015 16:03:07 +0800 [thread overview]
Message-ID: <20150402080307.GD2805@localhost.localdomain> (raw)
In-Reply-To: <150401084744.ZM30889@torch.brasslantern.com>
On Wed, Apr 01, 2015 at 08:47:44AM -0700, Bart Schaefer wrote:
> On Apr 1, 1:15pm, Peter Stephenson wrote:
> }
> } > And I have figured out this works:
> } >
> } > subcmd_dev=(
> } > /$'[[:alnum:][:punct:][:cntrl:][:digit:]]##\0'/
> } > -'if [[ $words[CURRENT-1] = dev ]];then false;else true;fi'
> } > ':interfaces:network interface:_net_interfaces'
> } > )
> }
> } I didn't even know what format guards could take in general...
>
> They're just passed to "eval" and the exit status checked. If false,
> the pattern is presumed not to match. The pattern is evaluated with
> backreferences enabled, so normally you'd refer to $match in the guard,
> but in this case maybe we want to examine previous words rather than
> the one to which the pattern is being applied.
>
> subcmd_dev=(
> /$'[[:alnum:][:punct:][:cntrl:][:digit:]]##\0'/
> -'[[ $words[CURRENT-1] != dev ]]'
> ':interfaces:network interface:_net_interfaces'
> )
>
> should be equivalent, but I suspect we might really want to examine the
> whole array slice $words[2,CURRENT-1] to see if "dev" appears anywhere.
If using -'[[ $words[2,CURRENT-1] != *dev* ]]', then "dev" and "up"
won't be completed after dev (this is right, dev after dev is wrong
syntax), but there is a prase failed warning :
% ip link show dev em1 <tab>
parse failed before current word
next prev parent reply other threads:[~2015-04-02 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 3:39 Han Pingtian
2015-03-31 1:27 ` Eric Cook
2015-03-31 4:52 ` Bart Schaefer
2015-04-01 0:52 ` Han Pingtian
2015-03-31 18:57 ` Peter Stephenson
2015-04-01 10:07 ` Han Pingtian
2015-04-01 12:15 ` Peter Stephenson
2015-04-01 15:47 ` Bart Schaefer
2015-04-02 8:03 ` Han Pingtian [this message]
2015-04-02 16:55 ` Bart Schaefer
2015-04-02 17:00 ` Peter Stephenson
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=20150402080307.GD2805@localhost.localdomain \
--to=hanpt@linux.vnet.ibm.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).