From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: "antecedents" [was Re: a couple of completion questions]
Date: Thu, 8 Jun 2000 11:36:31 +0200 (MET DST) [thread overview]
Message-ID: <200006080936.LAA19790@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Clint Adams's message of Wed, 7 Jun 2000 11:06:50 -0400
Clint Adams wrote:
> > Sorry, I don't understand... what do you want to do?
>
> Okay. I want to use _arguments -A in the state switch at the bottom.
> Originally, install and record_avail were the same case, but when I
> added -A, they wouldn't complete, so I had to insert the options
> that had gotten the user to that state, which is why install and
> record_avail are two separate cases now.
>
> I want to avoid making remove, purge, status, and listfiles
> four separate cases, yet still retain the -A to _arguments.
> My last resort would probably be to define four new arrays with
> the short and long options and then use something like
> ${(P)${:-_dpkg_actions_${state}}}, but I was hoping that there
> was a better way.
Aha. Well, if it finds a string not described by one of the
option-specs it has to take it to be an argument.
Hm, should we add an option, to be combined with -A (or an argument to
-A?) to tell it that it should consider words starting with [-+] to be
arguments? Or, probably better, let -A take an argument, a pattern and
all words matching it are not taken to be arguments and hence don't
keep it from completing option.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-06-08 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 9:36 Sven Wischnowsky [this message]
2000-06-08 17:41 ` Clint Adams
-- strict thread matches above, loose matches on Subject: below --
2000-06-07 8:50 a couple of completion questions Sven Wischnowsky
2000-06-07 15:06 ` "antecedents" [was Re: a couple of completion questions] Clint Adams
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=200006080936.LAA19790@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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).