From: Sven Wischnowsky <wischnow@berkom.de>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: _file_systems & Re: zstyle for _arguments feature request
Date: Thu, 10 Jan 2002 14:46:07 +0100 [thread overview]
Message-ID: <15421.39711.249899.991670@wischnow.berkom.de> (raw)
In-Reply-To: <20020109071947.43798.qmail@web10406.mail.yahoo.com>
Felix Rosencrantz wrote:
> Sven Wischnowsky wrote:
> >Err... pardon? ;-) Could you give us a code snippet to easily
> >reproduce this? I currently don't have that much time, sorry.
>
> Sorry about that. I'm writing from another system.
> Here's something a little more specific.
>
> I tried using the default completion for "enscript --font"
>
> @ enscript --font []<TAB>
> ---- fontname
> @ zstyle :completion::complete:enscript:option--font-1:option--font-1 fake
> 'font3:This is font3' font4:Four font5
> @ enscript --font []<TAB>
> ---- fontname
> ---- fontname
> <Then the correct font*'s are listed...>
>
> Notice the "---fontname" description listed twice, and the need to specify the
> "option--font-1" twice in the zstyle. Something looks like it is being called
> twice incorrectly.
Urgh.
1. The doubled `option-...' doesn't bother me a lot, that's just
_arguments using the only sensible thing it knows about as the
tag. Users can always use `:completion:...:*'.
2. The doubled description is the real problem. There is no action in
the spec for --font. So the faked matches get added under that
default description mentioned above and later _arguments uses
message to add the explanation it always adds for an empty action
in a spec. And that's the reason why the C code doesn't put the
two groups together, which was irritating me before I looked.
Hrm. I've got to think some more about this, or maybe someone else
has ideas?
Bye
Sven
--
Sven Wischnowsky wischnow@berkom.de
next prev parent reply other threads:[~2002-01-10 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 7:19 Felix Rosencrantz
2002-01-10 13:46 ` Sven Wischnowsky [this message]
2002-01-14 12:34 ` Oliver Kiddle
2002-01-18 8:47 ` Sven Wischnowsky
-- strict thread matches above, loose matches on Subject: below --
2002-01-22 2:35 Felix Rosencrantz
2002-01-28 16:37 ` Sven Wischnowsky
2002-01-08 6:26 Felix Rosencrantz
2002-01-08 8:26 ` Sven Wischnowsky
2001-12-11 15:38 Wischnowsky, Sven
2001-12-11 15:24 Oliver Kiddle
2002-01-07 14:45 ` Sven Wischnowsky
2002-01-07 14:47 ` Sven Wischnowsky
2002-01-07 16:06 ` Oliver Kiddle
2002-01-21 16:09 ` Sven Wischnowsky
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=15421.39711.249899.991670@wischnow.berkom.de \
--to=wischnow@berkom.de \
--cc=zsh-workers@sunsite.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).