zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: 3.1.6-dev-18
Date: Tue, 15 Feb 2000 10:43:56 +0100 (MET)	[thread overview]
Message-ID: <200002150943.KAA11806@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Mon, 14 Feb 2000 19:10:49 +0000


Peter Stephenson wrote:

> ...
>
> 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.

Hopefully, giving the same string more than once wouldn't make sense.

> 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.

I can only repeat... I would have no problems with turning the matcher 
style as used by _matcher (or even renaming it for clarity) into one
that is used as an array. The first _matcher would then use the first
string in the value, the second one the second string and so on. I
just thought -- and I may very well be wrong here -- that it would
make users more aware of what they are doing if we use this more
explicit setting we have now. I.e., even with the suggested
array-interpretation of the matcher style one would have to add a new
call to _matcher in the completer list when adding a new string to the 
matcher style.

Hm. If anyone now says: change it, I will (renaming the style so that
it doesn't look like the matcher style used for tags -- which is
looked up as a string).

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-02-15  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-15  9:43 Sven Wischnowsky [this message]
2000-02-15 10:29 ` 3.1.6-dev-18 Andrej Borsenkow
2000-02-15 21:58 ` 3.1.6-dev-18 Peter Stephenson
  -- 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-14  9:38 3.1.6-dev-18 Sven Wischnowsky
2000-02-14 19:10 ` 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=200002150943.KAA11806@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --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).