From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: 3.1.6-dev-18
Date: Mon, 14 Feb 2000 19:10:49 +0000 [thread overview]
Message-ID: <E12KQq0-0006pa-00.2000-02-14-19-07-12@cmailg2.svr.pol.co.uk> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Mon, 14 Feb 2000 10:38:20 +0100." <200002140938.KAA08906@beta.informatik.hu-berlin.de>
Sven Wischnowsky wrote:
> Peter Stephenson wrote:
>
> > zstyle ':completion:*' completer _matcher ....
> > zstyle ':completion:*' matcher blah1 blah2 ...
>
> This would have a different effect... See 9657 and follow-ups (or the
> docs). It's something like:
>
> zstyle ... completer _matcher _complete _matcher _complete ...
> zstyle ':completion:*:matcher-1:*' matcher blah1
> zstyle ':completion:*:matcher-2:*' matcher blah2
>
> If this looks weird to anyone, please join the discussion in 9678,
> 9679 and tell us what you think about what I said in the latter.
It took me a while to work out what you were saying, but I think it's that
while `blah1 blah2' used to be tried one after another when they were
elements of $compmatchers, they get tried all at once if they are elements
of the matcher style in the form I gave it. If that's correct, I doubt if
that's a major issue for most users --- I suspect that most people who used
more than one element of $compmatchers just had different things in them,
as I did.
Still, how much do you gain by being able to put them in matcher-1 and
matcher-2? Is that more powerful than just using array elements of the
style in order, rather than simply more cumbersome? The only examples I
can think of where you gain something are where _matcher is followed the
second time by _prefix instead of _complete (or vice versa), or where some
other element of the context is different between the matcher-1 and
matcher-2 cases. These seem to me to be to abstruse to be useful. But I
may well have missed something.
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
next prev parent reply other threads:[~2000-02-14 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-14 9:38 3.1.6-dev-18 Sven Wischnowsky
2000-02-14 19:10 ` Peter Stephenson [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-17 10:58 3.1.6-dev-18 Sven Wischnowsky
2000-02-16 10:50 3.1.6-dev-18 Sven Wischnowsky
2000-02-16 17:41 ` 3.1.6-dev-18 Peter Stephenson
2000-02-15 11:47 3.1.6-dev-18 Sven Wischnowsky
2000-02-15 9:43 3.1.6-dev-18 Sven Wischnowsky
2000-02-15 10:29 ` 3.1.6-dev-18 Andrej Borsenkow
2000-02-15 21:58 ` 3.1.6-dev-18 Peter Stephenson
2000-02-11 19:38 3.1.6-dev-18 Peter Stephenson
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=E12KQq0-0006pa-00.2000-02-14-19-07-12@cmailg2.svr.pol.co.uk \
--to=pws@pwstephenson.fsnet.co.uk \
--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).