From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: Add CORRECT_NOCOMPSYS option
Date: Mon, 6 Apr 2009 10:09:29 +0100 [thread overview]
Message-ID: <20090406100929.505617e2@news01> (raw)
In-Reply-To: <090405151115.ZM13159@torch.brasslantern.com>
On Sun, 05 Apr 2009 15:11:15 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Apr 5, 7:13pm, Peter Stephenson wrote:
> }
> } Right, here's a more general solution. Shout if I've missed something.
>
> Looks reasonable to me. Should it be made clearer that this does not
> apply to the CORRECT_ALL option?
I added the sentence
The pattern does not apply the correction
of file names, as applied by the tt(CORRECT_ALL) option (so with the
example just given files beginning with `tt(_)' in the current
directory would still be completed).
> I was just looking at adding something to _setup to copy the value of
> CORRECT_IGNORE into the ignored-patterns style, but that suffers from
> the same bootstrapping issues as MENUSELECT and ZLS_COLORS. So maybe
> it would just be better to document it somewhere.
>
> Or perhaps it would be good enough simply to set it if it is not set:
>
> if ! zstyle -m ':completion:*:-command-:*' ignored-patterns '*'
> then
> zstyle ':completion:*:-command-:*' ignored-patterns '_*'
> fi
Or maybe use $CORRECT_IGNORE here if set and maybe allow ignored-patterns
to be set in such a way that it won't do that.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
next prev parent reply other threads:[~2009-04-06 9:09 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 [this message]
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
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=20090406100929.505617e2@news01 \
--to=pws@csr.com \
--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).