From: Wayne Davison <wayned@users.sourceforge.net>
To: Zsh Workers <zsh-workers@sunsite.auc.dk>
Subject: Space-expansion problem in dev-8
Date: Thu, 1 Feb 2001 09:41:14 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.21.0102010930180.8191-100000@phong.blorf.net> (raw)
I just upgraded from dev-7 to dev-8 to try to fix the following problem,
but it is still there.
If a filename contains spaces (or other escapable characters) and you
expand it via wild-carding, the spaces are not escaped.
For instance:
% zsh -f
% touch 'a b c d e'
% autoload -U compinit
% compinit
% zstyle ':completion:*' completer _expand _complete
% bindkey '\t' complete-word
% ls a*<TAB>
One of the offered suggestions is "a b c d e" rather than "a\ b\ c\ d\ e".
If I complete it without the '*' or expand it without changing tab's key
binding, it works properly.
..wayne..
next reply other threads:[~2001-02-01 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 17:41 Wayne Davison [this message]
2001-02-01 17:57 ` Peter Stephenson
2001-02-02 8:21 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=Pine.LNX.4.21.0102010930180.8191-100000@phong.blorf.net \
--to=wayned@users.sourceforge.net \
--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).