From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: ignored-patterns giving correction a go
Date: Fri, 17 Mar 2000 10:05:00 +0100 (MET) [thread overview]
Message-ID: <200003170905.KAA01669@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Oliver Kiddle's message of Thu, 16 Mar 2000 19:03:01 +0000
Oliver Kiddle wrote:
> I added the following to by .zshrc after seeing it in Peter's Zsh Guide
> as an example:
>
> zstyle ':completion:*:functions' ignored-patterns '_*'
>
> This is often very useful because I don't get functions beginning with
> underscores until I've actually typed the underscore. The trouble is
> that the correction completer gets to have a go before completion is
> tried without the ignored-patterns so for e.g which _co<tab> offers me
> corrections such as co. Is there any way around this?
See 9865.
I use something like:
zstyle :completion::::: completer _next_tags _expand _complete \
_complete _match _correct \
_approximate _prefix
zstyle ':completion:*:complete-2:*' prefer-ignored yes
zstyle ':completion:*:(correct|approximate|prefix)-1:*' prefer-ignored yes
(Simpler setups can obviously be thought of ;-)
All this alternate-set stuff looks like a hack. Initially it was
invented for $fignore with compctl, but I really, really think we
could do it better now with the completion system. And we should do it
better, I think, it probably the most important part of 10134, for me
at least. The problem is that if we remove the alternate set stuff for
new completion, we'll have trouble re-implementing the behaviour of
$fignore, at least when we want it to have the exact same effect.
Some more about 10134: after having thought about it some more, I
begin to like the suggestion with `tag-order tag=method ...' with the
shortcut `tag-order foo'. If I'm not completely mistaken, it would
allow us to change the internals, allow much better control and still
don't invalidate anyone's setup. I think I'll play a bit with this at
the weekend.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev reply other threads:[~2000-03-17 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-14 14:19 tags and all that Sven Wischnowsky
2000-03-17 9:05 ` Sven Wischnowsky [this message]
2000-03-17 18:20 ` ignored-patterns giving correction a go Bart Schaefer
2000-03-17 18:47 ` PATCH: Documentation for completer field of context Bart Schaefer
2000-03-16 19:03 ignored-patterns giving correction a go Oliver Kiddle
2000-03-21 10:00 Sven Wischnowsky
2000-03-21 16:01 ` Bart Schaefer
2000-03-21 16:10 Sven Wischnowsky
2000-03-21 16:46 ` Bart Schaefer
2000-03-22 13:32 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=200003170905.KAA01669@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).