From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _arguments problems
Date: 04 Feb 2000 22:16:39 +0900 [thread overview]
Message-ID: <rsq3dr9yuo8.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: Sven Wischnowsky's message of "Fri, 4 Feb 2000 10:59:39 +0100 (MET)"
In article <200002040959.KAA23014@beta.informatik.hu-berlin.de>,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
> > is27e1u11% _tst () { _arguments '-a' '*::rest:_tst2' }
> > is27e1u11% _tst2 () { compadd - '-b' }
> > is27e1u11% tst arg -<TAB>
> > -b
> > -a
> >
> > This completes `-a' and `-b' but it shouldn't completes `-a'.
>
> Hm. I see why you think it shouldn't and it can be achieved by
> applying the first hunk below.
>
> *But* if we do that there wouldn't be a way to get at the options in
> cases like this one (ok, it works with longer options but with short
> ones like these one would have to type the whole option to complete
> it). I'm really not sure if this is a good idea, I could only convince
> myself to build that patch because one can always set the
> prefix-needed style to false for such commands.
>
> I'd like to hear other opinions: does anyone think that this might
> surprise users? Or maybe I'm worrying too much about to special a
> case...
I intended to use that for _cvs. Since valid options are quite
different before and after non-option first argument, it is trouble
that _arguments in _tst1 and _cvs completes options over non-option
first argument. If _arguments behaves so, _cvs completes global
options for subcommands as:
Z(2):akr@is27e1u11% cvs add -<TAB>
option
--allow-root --help-options -H -a -e -l -q -t -x
--help --help-synonyms -Q -b -f -m -r -v -z
--help-commands --version -T -d -k -n -s -w
Options except `-k' and `-m' are global options and they are only
valid between `cvs' and `add'.
So, I think following behaviour is also problem.
is27e1u11% _tst () { _arguments '-a' '*::rest:(rest)' }
is27e1u11% tst arg -<TAB>
->
is27e1u11% tst arg -a
Because I think _arguments shouldn't completes options after an
argument handled by `*::message:action'.
--
Tanaka Akira
next prev parent reply other threads:[~2000-02-04 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-04 9:59 Sven Wischnowsky
2000-02-04 13:16 ` Tanaka Akira [this message]
2000-02-04 14:18 ` Sven Wischnowsky
2000-02-04 18:35 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-05-10 7:42 Tanaka Akira
2000-02-07 8:54 Sven Wischnowsky
2000-02-03 19:14 Tanaka Akira
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=rsq3dr9yuo8.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--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).