From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Completion issues
Date: Wed, 05 Apr 2000 19:30:00 +0100 [thread overview]
Message-ID: <E12cuYv-0001aR-00.2000-04-05-19-29-57@mail6.svr.pol.co.uk> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Mon, 03 Apr 2000 17:25:52 +0200." <200004031525.RAA32538@beta.informatik.hu-berlin.de>
Sven Wischnowsky wrote:
> Hm. Should we add a tag-labels style again (tested for every tag in
> tag-order, gives labels to use for this tag in its value)? My main
> reason for not liking this that much is the fact that it's in C now --
> I wanted to avoid having style-lookups hidden in some C-function.
As long as it works, which it does now, I'm not worried.
> > I would expect the following to work:
> > zstyle ':completion:*:sequences' tag-order sequences:-name sequences:-num
> > zstlye ':completion:*:sequences-name' ignored-patterns '<->'
> > zstyle ':completion:*:sequences-num' ignored-patterns '^<->'
This now works, too
> > Another thing: I couldn't get matcher-list to work for a labelled
> > completer, e.g. _complete:-extended.
This seems to work this time. Don't what I did wrong. So what's the
difference between matcher and matcher-list now? The latter is looked up
once for a completer (but again if we have a labelled completer), but the
latter is looked up every single time we add a match?
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Work: pws@CambridgeSiliconRadio.com
Web: http://www.pwstephenson.fsnet.co.uk
next prev parent reply other threads:[~2000-04-05 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 15:25 Sven Wischnowsky
2000-04-05 18:30 ` Peter Stephenson [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-06 7:31 Sven Wischnowsky
2000-04-04 9:49 Sven Wischnowsky
2000-04-03 13:11 Sven Wischnowsky
2000-04-03 12:56 Sven Wischnowsky
2000-04-01 20:26 Peter Stephenson
2000-04-02 3:16 ` Bart Schaefer
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=E12cuYv-0001aR-00.2000-04-05-19-29-57@mail6.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).