From: Wayne Davison <wayned@users.sourceforge.net>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: expansion
Date: Wed, 7 Jun 2000 15:21:09 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0006071444300.20381-100000@phong.blorf.net> (raw)
In-Reply-To: <200006070646.IAA11684@beta.informatik.hu-berlin.de>
On Wed, 7 Jun 2000, Sven Wischnowsky wrote:
> I wrote:
> > Finally, one of the just-committed cvs changes has introduced a bug
> > where an extra space is getting added when it shouldn't be. Now, if
> > you type "~/.z<tab>" you get "/home/wayne/.z " even though that file
> > does not exist.
>
> We are talking about *expansion* here.
Yes, I was switching topics a bit and talking about a bug in the
_expand module. When I type the string "ls ~/.z<tab>" hoping to
complete the filename, instead the _expand module expands the ~ into
my home directory, and it now adds a space to the end of the string.
That means I have to backspace over the space to continue completing
the filename.
> Wayne Davison wrote:
> > However, no matter what I try, tab does not expand wildcards with
> > expand-or-complete set.
>
> [Scratching head...] Hm. It works for me.
...And it would have worked for me too if glob_complete hadn't been
turned on in the /etc/zshrc file. I apparently didn't notice that
Mandrake Linux does this (because I have been attempting to use the
new expansion/completion system on my Linux box).
> [Going back to the glob discussion...]
> You can also try the substs-globs-only style.
I assume that should be spelled "subst-globs-only". I can't get this
style to work for me. If I only set subst-globs-only (without anything
like "glob" set), it does nothing. If I also set "glob", it expands
tildes. I.e.:
% zsh -f
% bindkey '\t' complete-word
% autoload -U compinit
% compinit -D
% zstyle ':completion:*' completer _expand _complete
% zstyle ':completion:*:expand:::' subst-globs-only 1
% zstyle ':completion:*:expand:*' tag-order all-expansions
% touch tmp{1..3}
% ls tmp*<tab>
This fails to do anything (but beep). If I add this line:
% zstyle ':completion:*:expand:::' glob 1
then "ls tmp*<tab>" expands correctly, but "~/.z<tab>" expands the
tilde instead of doing nothing.
..wayne..
next prev parent reply other threads:[~2000-06-07 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-07 6:46 PATCH: expansion (was: Re: PATCH: Re: blah*[TAB] (difference between 3.1.6 and 3.1.9)) Sven Wischnowsky
2000-06-07 7:07 ` Sven Wischnowsky
2000-06-07 15:28 ` Bart Schaefer
2000-06-07 15:31 ` Bart Schaefer
2000-06-07 22:21 ` Wayne Davison [this message]
2000-06-08 10:03 ` PATCH: expansion Oliver Kiddle
[not found] <0FVU001OT0DZC6@la-la.cambridgesiliconradio.com>
2000-06-08 16:50 ` Oliver Kiddle
2000-06-09 7:32 Sven Wischnowsky
2000-06-09 10:45 ` Oliver Kiddle
2000-06-13 11:24 Sven Wischnowsky
2000-06-13 16:41 ` Bart Schaefer
2000-06-14 6: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.0006071444300.20381-100000@phong.blorf.net \
--to=wayned@users.sourceforge.net \
--cc=wischnow@informatik.hu-berlin.de \
--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).