zsh-users
 help / color / mirror / code / Atom feed
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: Wed, 1 Apr 2015 08:52:41 +0800	[thread overview]
Message-ID: <20150401005241.GA2805@localhost.localdomain> (raw)
In-Reply-To: <150330215220.ZM28507@torch.brasslantern.com>

On Mon, Mar 30, 2015 at 09:52:20PM -0700, Bart Schaefer wrote:
> diff --git a/Completion/Unix/Command/_ip b/Completion/Unix/Command/_ip
> index 3b68c35..c0a28d3 100644
> --- a/Completion/Unix/Command/_ip
> +++ b/Completion/Unix/Command/_ip
> @@ -9,7 +9,8 @@
>  # Values encoding simple types
>  #
>  local -a subcmd_dev
> -subcmd_dev=(/$'[[:alnum:][:punct:][:cntrl:][:digit:]]##\0'/ ':interfaces:network interface:_net_interfaces')
> +subcmd_dev=(/$'[[:alnum:][:punct:][:cntrl:][:digit:]]##\0'/ ':interfaces:network interface:_net_interfaces' "|"
> +  /$'dev\0'/ ':interfaces:network interface:_net_interfaces')
>  
>  local -a subcmd_onoff
>  subcmd_onoff=(/$'(on|off)\0'/ ':onoff:state (on or off):(on off)')
> 
This works pretty good, besides "dev" will be completed after "dev".
> 
> I suspect there should be some way to use the "-GUARD" syntax to prevent
> "dev" from completing again after "dev" ("ip link show dev dev" doesn't
> make sense, does it?) but there's no example of using a guard, and as
> someone implied, offering too much (as long as it's not *TOO* much) is
> better than offering too little.

I found that we can use "-'false'" as the the guard here:

subcmd_dev=(/$'[[:alnum:][:punct:][:cntrl:][:digit:]]##\0'/ -'false'
':interfaces:network interface:_net_interfaces')

then only network device will be completed after dev:

% ip link show dev<tab>
network interface
em1     lo      tun0    wlp3s0

or even using "[]" as the pattern has the same effect:

subcmd_dev=(/$'[]'/ ':interfaces:network interface:_net_interfaces')

But both of them will report parsing error when trying to complete after
the interface:

% ip link show dev lo<tab>
parse failed before current word



  reply	other threads:[~2015-04-01  1:23 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 [this message]
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
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=20150401005241.GA2805@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).