From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: Add CORRECT_NOCOMPSYS option
Date: Thu, 28 May 2009 11:25:14 +0200 [thread overview]
Message-ID: <20090528092514.GA3315@fsst.voodoo.lan> (raw)
In-Reply-To: <2d460de70905280148iebfcegcb4143c33e510efd@mail.gmail.com>
Richard Hartmann <richih.mailinglist@gmail.com>:
> On Wed, May 27, 2009 at 21:12, Greg Klanderman <gak@klanderman.net> wrote:
>
> > But in the same vein, what I really want is a way to configure the
> > behavior for functions, variables, etc. beginning with "_" to be like
> > filenames beginning with ".": completion should work if I have
> > explicitly typed the leading "_", but even substring matching should
> > not *generate* a leading "_".
>
> I think this is a good explanation of what, imo, the final goal should
> be.
The final goal for what?
For completion (without looking at it in detail), I think what Greg
wants could be done with the _ignore completer. At least I got
something similar for a set of commands:
zstyle ':completion:*:complete:-command-::commands' \
ignored-patterns 'aptitude-*'
Because I never want to complete the commands named
aptitude-create-state-bundle or aptitude-run-state-bundle.
With the above style 'apti<tab>' always completes to 'aptitude'.
But 'aptitude-<tab>' offers the two commands mentioned earlier, too,
in case I really really want one of them.
My completer style looks like this:
zstyle ':completion:*' completer _expand _complete _ignored _approximate
Where _ignore is the important bit.
That's completion. Correction is a whole other deal. And
CORRECT_IGNORE is just for that. So you don't get completion functions
as _suggestions_ for _correction_. (E.g. you don't have vim installed
but you try to execute it, chances are that correction will ask you
'zsh: correct 'vim' to '_vim'? (YNEA)' - which is utterly useless and
annoying).
So, when you're talking about a final goal, IMHO, CORRECT_IGNORE is
quite a reasonable solution. And it *only* works on words in command
position (aka. the stuff 'setopt correct' does - words corrected by
'setopt correct_all' are not touched at all).
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2009-05-28 9:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 0:07 Frank Terbeck
2009-04-05 2:37 ` Bart Schaefer
2009-04-05 12:23 ` Frank Terbeck
2009-04-05 18:13 ` Peter Stephenson
2009-04-05 22:11 ` Bart Schaefer
2009-04-06 9:09 ` Peter Stephenson
2009-05-27 16:30 ` Richard Hartmann
2009-05-27 16:59 ` Peter Stephenson
2009-05-27 19:12 ` Greg Klanderman
2009-05-28 8:48 ` Richard Hartmann
2009-05-28 9:25 ` Frank Terbeck [this message]
2009-05-28 18:44 ` Greg Klanderman
2009-05-28 19:03 ` Frank Terbeck
2009-05-28 19:35 ` Peter Stephenson
2009-05-28 22:56 ` Greg Klanderman
2009-05-29 8:32 ` Peter Stephenson
2009-05-29 14:38 ` Greg Klanderman
2009-05-29 14:49 ` Peter Stephenson
2011-03-01 20:39 ` PATCH: zstyle to control completion of functions/parameters beginning with underscore Greg Klanderman
2011-03-01 21:11 ` Peter Stephenson
2011-03-01 22:07 ` Greg Klanderman
2011-03-02 1:05 ` Oliver Kiddle
2011-03-02 18:49 ` Greg Klanderman
2011-03-02 23:30 ` Bart Schaefer
2011-03-03 15:33 ` Greg Klanderman
2011-03-03 16:11 ` Greg Klanderman
2011-03-03 16:54 ` Bart Schaefer
2011-03-06 20:07 ` Greg Klanderman
2011-03-06 22:02 ` Bart Schaefer
2011-03-08 15:13 ` Greg Klanderman
2011-03-09 18:41 ` Greg Klanderman
2011-03-10 15:54 ` Bart Schaefer
2011-03-10 16:44 ` Greg Klanderman
2011-03-10 17:10 ` Bart Schaefer
2011-03-10 18:01 ` Greg Klanderman
2011-03-11 17:01 ` Greg Klanderman
2011-03-03 16:58 ` Oliver Kiddle
2011-03-02 1:13 ` Richard Hartmann
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=20090528092514.GA3315@fsst.voodoo.lan \
--to=ft@bewatermyfriend.org \
--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).