From: Matt Armstrong <matt@corp.phone.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-users@sunsite.auc.dk
Subject: Re: _arguments question
Date: Thu, 13 Jul 2000 08:20:03 -0700 [thread overview]
Message-ID: <20000713082003.A9067@corp.phone.com> (raw)
In-Reply-To: <200007130857.KAA25581@beta.informatik.hu-berlin.de>; from wischnow@informatik.hu-berlin.de on Thu, Jul 13, 2000 at 10:57:20AM +0200
On Thu, Jul 13, 2000 at 10:57:20AM +0200, Sven Wischnowsky wrote:
>
> Matt Armstrong wrote:
>
> > I have this completion function that I have a question on:
> >
> > _p4_submit () {
> > _arguments \
> > '(-i)-c[changelist#]:changelist #' \
> > '(-c)-i[input from stddin]' \
> > ':submit file:_files'
> > }
> >
> > I have made -i and -c mutually exclusive. How can I make all three
> > mutually exclusive? This command accepts only one of the three
> > possible arguments.
>
> To say that with either of the options, the argument may not be
> completed, you include either its number or a `:' in their exclusion
> lists (the `:' means that no argument at all may be completed after
> the option).
Ahh, neat trick. I would suggest adding this to the man page -- I
could not find it.
> To say that after the argument no option should be completed, there
> are at least two ways. Either you give it a exclusion list, too
> (`(-c -i):submit ...') or you use the -A option to _arguments:
>
> _arguments -A '' \
> '(: -i)-c[changelist#]:changelist #' \
> '(: -c)-i[input from stddin]' \
> ':submit file:_files'
>
> The argument given to -A (the '' in the example) can be used to give
> a pattern matching strings that should be silently accepted and
> should not be considered to be normal arguments. E.g. if there may
> be other options than the ones described, you would use `-A "-*"' to
> say that any string starting with a hyphen should be ignored when
> trying to determine if a string on the line is an argument or
> something else.
Thanks. :-( I should have seen that in the docs.
P.S. I was worried that this new completion stuff would take zsh too
far down the road of making zsh the "Emacs of shells." But now I am
beginning to really like it. Thanks for all the work you've put into
it -- this is not a trivial task.
--
matt
next prev parent reply other threads:[~2000-07-13 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 8:57 Sven Wischnowsky
2000-07-13 15:20 ` Matt Armstrong [this message]
2000-07-13 15:56 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-07-12 17:40 Matt Armstrong
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=20000713082003.A9067@corp.phone.com \
--to=matt@corp.phone.com \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-users@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).