From: Stefan `Sec` Zehl <sec@42.org>
To: zsh-workers@sunsite.dk
Subject: zsh 4.x bug in completion?
Date: Mon, 9 Jul 2001 20:33:06 +0200 [thread overview]
Message-ID: <20010709203306.A24119@matrix.42.org> (raw)
Hi,
I'm a long-time user of zsh, and like it very much. I noticed there was
a new release, and thought I should upgrade because some of the
minor shortcomings of the 3.0.x-series might have been fixed. So I
upgraded from zsh3.0.x to zsh4.0.2 and noticed that it behaves
completely different. While I detest changing so much of the integral
behaviour, most of this was configurable, so i could restore the old
behaviour, and regain my sanity.
One thing, though, looks like a bug to me, at least I found no way to
turn it off.
To verify it, I used plain setup except a different binding for tab:
| nuyen:~>zsh -f
| nuyen% echo $ZSH_VERSION
| 4.0.2
| nuyen% bindkey ^i expand-or-complete-prefix
Now we enter a command.
| nuyen% echo test
| test
Lets assume this fails due to lacking permissions. I want to prepend
"sudo " to this command (sudo runs its arguments as root)
So i go to the beginning of the line, and add "sud"-<TAB>. The line now
looks like this:
| nuyen% sudo echo test
With the cursor beeing on the "e" of echo.
Now hit enter.
| nuyen% sudoecho test
| zsh: command not found: sudoecho
zsh removes the space. I have no idea who had that brilliant idea.
I found no option to turn this off. The closest ones, auto_param_keys
and auto_remove_slash seem to have no effect on that.
Please help,
Sec
--
(Learn Lisp. (Really. (I'm serious. (Trust me. (It rocks all over.)))))
-- Matt Curtin <cmcurtin@interhack.net> on freebsd-chat
next reply other threads:[~2001-07-09 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 18:33 Stefan `Sec` Zehl [this message]
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
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=20010709203306.A24119@matrix.42.org \
--to=sec@42.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).