From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Bug#236350: zsh: _prefix completer broken?
Date: Sat, 6 Mar 2004 17:38:39 +0000 [thread overview]
Message-ID: <1040306173839.ZM5329@candle.brasslantern.com> (raw)
In-Reply-To: <20040306160540.GW19320@pimlott.net>
On Mar 6, 11:05am, Andrew Pimlott wrote:
} Subject: Re: Bug#236350: zsh: _prefix completer broken?
}
} 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.
The add-space style does default to true, and you're seeing exactly what
you should be seeing. What you (and possibly the documentation) missed
is that the add-space style applies only to the _expand and _prefix
completers, so its default setting makes no difference if you aren't
using one of those.
} Also, when the completion on prefix succeeds, as in the "egrefoo"
} example, there is a beep, unlike with a normal successful completion.
This I can reproduce with 4.0.7. However, I'm having some trouble getting
_any_ of this to work with 4.2.0-pre-3. Sample output:
schaefer<504> egrefoo
No matches for `external command', `builtin command', `shell function',
`alias', `suffix alias', `reserved word', `job', `parameter', `local
directory', `directory in cdpath', or `corrections'
Here's 4.0.7 for comparison:
schaefer[538] egrefoo
schaefer[538] egrepfoo
(with a feep)
(Aside - in 4.0.7 if I then go on and hit TAB again I get this:
schaefer[538] egrepfoo
_
Completing external command
(with the underscore showing the location of the cursor).)
In both 4.2.0-pre-3 and 4.0.7, my completion style looks like this:
zstyle ':completion:*' completer \
_oldlist _expand _complete _match _ignored _approximate _prefix
However, 4.2.0-pre-3 never gets beyond trying _approximate. The output
from complete-debug is nearly a megabyte, but it looks as if it gets to
this point in both versions:
: _approximate:75:while; [[ _comp_correct -le comax ]]
: _approximate:111; compstate[pattern_match]=''
: _approximate:113; return 1
: _main_complete:1; unfunction compadd
And then 4.2.0-pre-3 goes on like this:
: _main_complete:159:for for elif-then; ret=0
: _main_complete:160:for for elif-then; break 2 <-- doesn't happen in 4.0.7
: _main_complete:169; curcontext=:::
: _main_complete:170; nm=0
next prev parent reply other threads:[~2004-03-06 17:38 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
2004-03-06 17:38 ` Bart Schaefer [this message]
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=1040306173839.ZM5329@candle.brasslantern.com \
--to=schaefer@brasslantern.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).