From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Silly questions about _arguments & Co (and probably bugs)
Date: 13 Sep 1999 22:57:04 +0900 [thread overview]
Message-ID: <rsqaeqqnccu.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: Sven Wischnowsky's message of "Mon, 13 Sep 1999 13:56:58 +0200 (MET DST)"
In article <199909131156.NAA21019@beta.informatik.hu-berlin.de>,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
> Almost. There were two problems: with single-letter options
> PREFIX/SUFFIX weren't cleared before `_display' was called (so that
> (almost) no option matched) and the return value of `_display' wasn't
> used to find out that `_arguments' should create the list itself.
I found another problem.
Z:akr@is27e1u11% Src/zsh -f 2>z
is27e1u11% bindkey -e; fpath=($PWD/Completion/*(/)); autoload -U compinit; compinit -D; compdef _tst tst
is27e1u11% compconf group_matches=yes message_format='%d' description_format='%d' describe_options=yes
is27e1u11% patch -l<TAB>
option
-B -D -E -F -N -R -S -T -V -Y -Z -b -d -z
Completion candidates are not enough.
With `set -x', zsh reports:
...
+_arguments:680> uns=-ignore-whitespacel
...
Hm. Exclusive long options should not used for `uns'.
--
Tanaka Akira
next prev parent reply other threads:[~1999-09-13 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 11:56 Sven Wischnowsky
1999-09-13 13:57 ` Tanaka Akira [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-13 14:21 Sven Wischnowsky
1999-09-09 14:27 Sven Wischnowsky
1999-09-09 22:01 ` Tanaka Akira
1999-09-09 13:55 Sven Wischnowsky
1999-09-09 14:05 ` Andrej Borsenkow
1999-09-09 15:15 ` Andrej Borsenkow
1999-09-09 15:44 ` Tanaka Akira
1999-09-09 13:13 Andrej Borsenkow
1999-09-09 13:54 ` Tanaka Akira
1999-09-09 14:26 ` Andrej Borsenkow
1999-09-09 14:32 ` Tanaka Akira
1999-09-09 14:34 ` Andrej Borsenkow
1999-09-09 14:45 ` Tanaka Akira
1999-09-09 15:02 ` Andrej Borsenkow
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=rsqaeqqnccu.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).