From: Andrew Pimlott <andrew@pimlott.net>
To: Clint Adams <schizo@debian.org>
Cc: zsh-workers@sunsite.dk, 236350-forwarded@bugs.debian.org
Subject: Re: Bug#236350: zsh: _prefix completer broken?
Date: Sat, 6 Mar 2004 11:05:40 -0500 [thread overview]
Message-ID: <20040306160540.GW19320@pimlott.net> (raw)
In-Reply-To: <20040306013513.GA25297@scowler.net>
On Fri, Mar 05, 2004 at 08:35:13PM -0500, Clint Adams wrote:
> > zstyle ':completion:*' completer _complete _prefix
> >
> > However, it doesn't seem that _prefix is having any effect. According
> > to everything I've read, I should be able to type "vfoo", put the cursor
> > over the 'f', hit tab, and get offered completions like "vi", etc.
> > Instead, I just get a beep.
>
> If you setopt COMPLETE_IN_WORD, it will complete vi, but otherwise, it
> doesn't appear that $SUFFIX is being set.
I really don't know how I missed that in the documentation and all the
searches I did, but when I setopt COMPLETE_IN_WORD, it indeed does work.
I guess the bug is only that compinstall doesn't generate a complete
configuration for _prefix. It would probably also be useful to move the
mention of COMPLETE_IN_WORD higher in the documentation for _complete,
and include it in the examples.
I noticed a couple other things. The documentation says that the
add-space style defaults to true. This doesn't seem to be the case, as
if I complete with the cursor on 'f' in "egrefoo", I get just "p" by
default, and "p " with
zstyle ':completion:*' completer _complete _prefix
in my config.
Also, when the completion on prefix succeeds, as in the "egrefoo"
example, there is a beep, unlike with a normal successful completion.
This is distracting.
Thanks for your help.
Andrew
next prev parent reply other threads:[~2004-03-06 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1AzKUu-0003tz-00@techloaner2.idiomtech.com>
2004-03-06 1:35 ` Clint Adams
2004-03-06 16:05 ` Andrew Pimlott [this message]
2004-03-06 17:38 ` Bart Schaefer
2004-03-06 17:59 ` Bart Schaefer
2004-03-06 18:03 ` Oliver Kiddle
2004-03-06 23:32 ` Bart Schaefer
2004-03-08 10:41 ` Peter Stephenson
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=20040306160540.GW19320@pimlott.net \
--to=andrew@pimlott.net \
--cc=236350-forwarded@bugs.debian.org \
--cc=schizo@debian.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).