From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: destructive list-expand
Date: Wed, 16 May 2001 19:14:19 +0000 [thread overview]
Message-ID: <1010516191419.ZM14926@candle.brasslantern.com> (raw)
In-Reply-To: <200105161024.MAA12568@beta.informatik.hu-berlin.de>
On May 16, 12:24pm, Sven Wischnowsky wrote:
} Subject: Re: destructive list-expand
}
} Bart Schaefer wrote:
}
} > This now gives the right thing for me with list-expand, but still fails
} > on _list_expansions (or _expand_word).
}
} Yes, I pointed that out and the reason for it: _expand uses
}
} eval 'exp=( ${${(e)exp//\\[
} ]/ }//(#b)([
} ])/\\$match[1]} )' 2>/dev/null
Could we change that to:
eval "exp=( $exp )" 2>/dev/null
eval 'exp=( ${$exp//\\[
]/ }//(#b)([
])/\\$match[1]} )' 2>/dev/null
Or is that going to break something else? (It fixes the specific example
we've been using, but I haven't tried any other examples e.g. that really
do have carriage-returns or other backslashed-whitespace in the results.)
--
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
prev parent reply other threads:[~2001-05-16 19:14 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
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 ` Bart Schaefer [this message]
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=1010516191419.ZM14926@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).