zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <Peter.Stephenson@csr.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Completing multiple states with _arguments
Date: Wed, 10 Nov 2010 12:11:07 +0000	[thread overview]
Message-ID: <20101110121107.3303c6c5@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <AANLkTimr25=Yab5DHRHg+SOPioh-C6byZ+ieGr+KmtPA@mail.gmail.com>

On Wed, 10 Nov 2010 12:23:50 +0100
Nikolai Weibull <now@bitwi.se> wrote:
> >> local context state line
> >> typeset -A opt_args
> >>
> >> _arguments \
> >>   ':: :->something-optional-before-files' \
> >>   '*:: :->file' && ret=0
> >>
> >> # Now what?
> 
> Is it as simple as
> 
> local s
> for s in $state; do
>   case $s in … esac
> done
> 
> or do you need to deal with tags and such through _alternative or so?

I think you do need to set up tags here, at least most scripts do and I
haven't tried without.  However, that should all be standard: looping
over the states is fine, then use the usual _wanted stuff inside the
case and the tags get sorted out automatically, in principle.  There's
nothing to stop you using _alternative, either.

In short, just adding the loop over the state to the sort of stuff that
usually appears in the "case" here should be OK.

-- 
Peter Stephenson <pws@csr.com>            Software Engineer
Tel: +44 (0)1223 692070                   Cambridge Silicon Radio Limited
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK


Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom


  reply	other threads:[~2010-11-10 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 22:49 Nikolai Weibull
2010-11-10 10:20 ` Peter Stephenson
2010-11-10 11:23   ` Nikolai Weibull
2010-11-10 12:11     ` Peter Stephenson [this message]
2010-11-10 12:37       ` Nikolai Weibull

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=20101110121107.3303c6c5@pwslap01u.europe.root.pri \
    --to=peter.stephenson@csr.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).