From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: destructive list-expand
Date: Tue, 15 May 2001 04:48:12 +0000 [thread overview]
Message-ID: <1010515044812.ZM11090@candle.brasslantern.com> (raw)
In-Reply-To: <20010514223000.A18323@dman.com>
On May 14, 10:30pm, Clint Adams wrote:
}
} If I type a command such as
}
} echo ${(M)${(f)"$(<listofthings)"}:#*subthing*}
}
} Then invoke list-expand, the appropriate expansion will be displayed,
} and the command line will change to
}
} echo ${(M)${(f)$(<listofthings)}:#*subthing*}
Hmm; this is interesting.
list-expand (C-x g) doesn't use the new completion system, and exhibits
the above-described behavior at least as far back as 3.0.6 and probably
farther.
_list_expansions (C-x d) from _expand_word should be the new completion
system equivalent, but it doesn't appear to work at all. Even just plain
_expand_word (C-x e) beeps at me, but old-style expand-word properly
expands to everything listed by list-expand.
It's a bit hard to tell from the _complete_debug trace, but it looks as
if the double quotes have already been stripped from $PREFIX by the time
_expand is called -- e.g.
: _expand:24:else; word=${(M)${(f)$(<listofthings)}:#*subthing*}
and then a bit later
: _expand:60:then; exp=: _expand:60:then cmdsubst; print -l CVS ChangeLog
ChangeLog-Release ChangeLog.3.0 Completion Config Doc Etc Functions INSTALL
LICENCE META-FAQ Makefile.in Misc README Src StartupFiles Test Util acconfig.h
aclocal.m4 aczsh.m4 config.guess config.h.in config.log config.sub configure
configure.in full.diff install-sh mkinstalldirs stamp-h.in
: _expand:60:then; exp=( )
I don't quite see where the quotes are getting stripped off, unless it's
actually get_comp_string() that's at fault. (Somebody (hi, Sven) should
update the comment around line 1028 of zle_tricky.c in any event.)
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-05-15 4:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 2:30 Clint Adams
2001-05-15 4:48 ` Bart Schaefer [this message]
2001-05-15 5:32 ` Bart Schaefer
2001-05-15 9:28 ` Sven Wischnowsky
2001-05-15 13:48 ` Sven Wischnowsky
2001-05-15 13:57 ` Peter Stephenson
2001-05-15 14:18 ` Sven Wischnowsky
2001-05-15 14:41 ` Bart Schaefer
2001-05-15 15:05 ` Bart Schaefer
2001-05-16 10:24 ` Sven Wischnowsky
2001-05-16 11:05 ` Peter Stephenson
2001-05-16 12:49 ` Sven Wischnowsky
2001-05-16 19:10 ` Quoting and ${(e)param} (was Re: destructive list-expand) Bart Schaefer
2001-05-17 9:03 ` Sven Wischnowsky
2001-05-18 9:55 ` Bart Schaefer
2001-05-18 12:36 ` PATCH: " Sven Wischnowsky
2001-05-16 19:14 ` destructive list-expand Bart Schaefer
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=1010515044812.ZM11090@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).