From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Path completion causing ambiguous path tail to disappear
Date: Mon, 21 Feb 2000 04:11:19 +0000 [thread overview]
Message-ID: <1000221041119.ZM21973@candle.brasslantern.com> (raw)
This is not exactly a complaint, because I can (almost) get the behavior I
want by using a style ... rather it's a question of whether the default
behavior should be different.
I have my zsh sources under /usr/src/local/zsh/. With dev-19:
zagzig[36] cd /usr/s/l/<TAB>
The valid completions at this point should be
/usr/src/local /usr/src/linux /usr/share/libtool /usr/share/locale
However, what happens is that the word on the command line is *shortened*,
leaving me with
zagzig[36] cd /usr/s/
with the cursor on top of the final `/'. Now, I don't mind the cursor
moving back to that point if that's where I need to disambiguate, but I
was surprised that zsh deleted the tail of the path rather than simply
feeping, or displaying the list.
Note that if I start with no trailing slash, i.e.
zagzig[36] cd /usr/s/l<TAB>
*then* the behavior is what I expect; the cursor moves back to the `/'
but the `l' remains on the line.
If I use
zstyle ':completion:*:paths' expand prefix
Then I get the behavior I want from expand-or-complete, but not from
complete-word (which causes predict-on to break, which is how I really
noticed all of this in the first place).
Why does the trailing slash cause the `l/' to be deleted?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next reply other threads:[~2000-02-21 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-21 4:11 Bart Schaefer [this message]
2000-02-21 7:26 ` Andrej Borsenkow
2000-02-21 9:12 Sven Wischnowsky
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=1000221041119.ZM21973@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.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).