From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: zsh 4.x bug in completion?
Date: Tue, 10 Jul 2001 08:10:54 +0000 [thread overview]
Message-ID: <1010710081054.ZM28108@candle.brasslantern.com> (raw)
In-Reply-To: <Pine.SV4.4.33.0107100922120.22525-100000@itsrm2.mow.siemens.ru>
I get very strange behavior from 4.0.2.
With
zstyle ':completion:*' completer _complete _prefix
I get:
schaefer<503> <Ctrl-P>
schaefer<503> echo foo<Ctrl-A>
schaefer<503> sud<TAB>echo foo
schaefer<503> sudoecho foo
^
cursor here
That is, it inserts `sudo' with no trailing space, but then moves to
the end of the word `echo' and adds a space *there*. That is almost
certainly wrong?
I get exactly the same thing from 4.1.0-dev-2.
If I then add
zstyle ':completion:*' add-space yes
I get `sudo echo foo', that is, it has added a space both after `sudo'
and after `echo'.
And, by the way, with TAB bound to expand-or-complete-prefix, I can in
fact reproduce the original complaint. Auto-removing the space may make
sense when completing in the middle of a file path, but it doesn't when
completing in command position.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-07-10 8:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 18:33 Stefan `Sec` Zehl
2001-07-09 18:49 ` Andrej Borsenkow
2001-07-09 18:54 ` Peter Stephenson
2001-07-09 19:31 ` Oliver Kiddle
2001-07-10 5:24 ` Andrej Borsenkow
2001-07-10 8:10 ` Bart Schaefer [this message]
2001-07-10 9:19 ` Sven Wischnowsky
2001-07-10 9:32 ` Peter Stephenson
2001-07-10 16:33 ` Bart Schaefer
2001-07-11 8:20 ` Sven Wischnowsky
2001-07-10 5:54 ` Thomas Köhler
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=1010710081054.ZM28108@candle.brasslantern.com \
--to=schaefer@candle.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).