From: Wayne Davison <wayned@users.sourceforge.net>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: Zsh Workers <zsh-workers@sunsite.auc.dk>
Subject: Re: Another keep-prefix problem
Date: Tue, 24 Apr 2001 12:18:48 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.30.0104241130360.3333-100000@phong.blorf.net> (raw)
In-Reply-To: <1010424165026.ZM5732@candle.brasslantern.com>
In reading through the man page some more, it looks like in this case
I should be complaining about the "suffix" style: that it requires
the word to start with a $ or a ~ for this rule to kick in.
The old expander does not require this. I.e. it treats this as a
completion request (use expand-or-complete without _expand in your
completer setting):
% ls -l /net/machine$path/foo<TAB>
This does not expand anything. I think that it will cause less
confusion if the new expander would work like the old one does in
this regard.
However, I have the same complaint about keep-prefix when using
wildcards:
% ls -l /net/machine$path/foo*<TAB>
I'd like to see $path left unexpanded. In other words, I want keep-
prefix to preserve the prefix no matter where the $ expression is in
the prefix.
> Maybe you want to look at the `subst-globs-only' and/or `substitute'
> styles, if you haven't already done so.
I suppose using subst-globs-only might be a fairly good way to go
(along with changing ^Xe to something that would actually expand
variables -- using "expand-word" seems to work fine). However, using
this setting does still "fail" my glob-expansion test above (i.e. it
does not leave the $path unexpanded when expanding wildcards).
Using "substitute false" appears to break wildcards with variables
completely, so that doesn't appear to be useful to me.
..wayne..
next prev parent reply other threads:[~2001-04-24 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 0:46 Wayne Davison
2001-04-24 16:50 ` Bart Schaefer
2001-04-24 19:18 ` Wayne Davison [this message]
2001-04-25 13:25 ` Sven Wischnowsky
2001-04-26 4:33 ` Bart Schaefer
2001-04-26 14:27 Oliver Kiddle
2001-04-26 15:43 ` Wayne Davison
2001-04-26 17:18 ` Bart Schaefer
2001-04-26 23:38 ` Wayne Davison
2001-04-27 9:03 ` 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.30.0104241130360.3333-100000@phong.blorf.net \
--to=wayned@users.sourceforge.net \
--cc=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).