From: Greg Klanderman <gak@klanderman.net>
To: zsh-workers@zsh.org
Subject: Re: PATCH: zstyle to control completion of functions/parameters beginning with underscore
Date: Wed, 09 Mar 2011 13:41:48 -0500 [thread overview]
Message-ID: <m31v2gt9ub.fsf@klanderman.net> (raw)
In-Reply-To: <110306140249.ZM8874@torch.brasslantern.com> (Bart Schaefer's message of "Sun, 06 Mar 2011 14:02:49 -0800")
>>>>> On March 6, 2011 Bart Schaefer <schaefer@brasslantern.com> wrote:
> It's fine.
Well, maybe not :-(
I've noticed some bugginess with this:
| zsh -f
| phl% autoload -U compinit
| phl% compinit -u
| phl% function foobar () { echo foobar }
OK, now hit <tab> to complete after 'foobar':
| phl% foobar<tab>
and it adds a space.
now,
| phl% zstyle ':completion:*' prefix-needed true
and try completing 'foobar' again:
| phl% foobar<tab>
and it just beeps.
If I change _command_names to instead declare a local 'funcnames' and
change the prefix-needed logic to:
| if zstyle -t ":completion:${curcontext}:functions" prefix-needed && \
| [[ $PREFIX != [_.]* ]] ; then
| funcnames=(${(k)functions[(I)[^_.]*]})
| else
| funcnames=(${(k)functions})
| fi
and change the compadd in defs for functions to 'compadd -a funcnames',
then it works fine.
Completion of 'foobar' after 'unfunction' (i.e. using the equivalent
change made to _functions) however works fine.
So it seems like compadd's handling of the -k with subscript is not
always working properly.
My parameter completion change seems to be unaffected; which makes
sense since it's directly adding the completions to the compadd
invocation.
thanks,
Greg
next prev parent reply other threads:[~2011-03-09 18:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 0:07 PATCH: Add CORRECT_NOCOMPSYS option 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
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 [this message]
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=m31v2gt9ub.fsf@klanderman.net \
--to=gak@klanderman.net \
--cc=zsh-workers@zsh.org \
/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).