Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [^ax-y] doesn't work but [^x-ya] does
- X-seq: zsh-workers 40693
- From: Sebastian Gniazdowski <psprint3@xxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: [^ax-y] doesn't work but [^x-ya] does
- Date: Thu, 02 Mar 2017 03:22:13 -0800
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=CbTFJaaq1NgVPqzCLCC6g6g08e 4=; b=wR+w5XGeWrvxtGy8BYQrckch1SdA5RYW6NsTFWCaM0xixQeHGlmLfw1UDD xrC/tvF9Y3DP7jICYzSVKq9h1ZXqedzZ9BZ9c0XZgay3SgV9jmIiGXD4+m+dz7hd Xw0LqcauRjBCiqASj0rf8e2T2JwkmJ5LpiiH+vufF6j2n7Slo=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=Cb TFJaaq1NgVPqzCLCC6g6g08e4=; b=es5d4VSDMH7vsV6XTS5aWR2UYijrSl9mnQ mBtH2L2YobQmcC5E8JqyGZPig6xC5DcJgR7lutKYbwDCPSd/LNkYrkBTXnrrLzh+ Cq1Ywn47zD0ndm090Z3AC7W2jarY8/uQTYCL/9y/Znn3pYCSrti3xxrqcxAQ81+6 w/XcEt3RA=
- In-reply-to: <20170302104710.6eed8ece@pwslap01u.europe.root.pri>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CGME20170302073436epcas2p1ee2d6d723bc7b0865e11243777a08417@epcas2p1.samsung.com> <1488440005.4187177.897775384.2538F781@webmail.messagingengine.com> <20170302104710.6eed8ece@pwslap01u.europe.root.pri>
On Thu, Mar 2, 2017, at 02:47 AM, Peter Stephenson wrote:
> Isn't the same problem showing up here? Watch closely, I may be missing
> the point...
(...)
> % print ${value//[${foo}b-z]/x}
> xc
>
> Oops, should be a combination of the above effects, giving xx, which is
> what you get if you expand the ${foo} by hand...
Yes exactly. With the addition that following works:
# print ${value//[b-z${foo}]/x}
xx
> Unfortunately tracking down where this came in isn't much help as we
> need to be able to get the correct overall effect of either Dash or
> literal '-' in all cases, rather than just moving the problem around.
Looked at code few times when debugging, had an unexamined impression
that sister variable of "seen_brct" is needed:
- if (!in_brace_param)
- in_brace_param = bct;
+ if (!in_brace_param) {
+ if ((in_brace_param = bct))
+ seen_brct = 0;
+ }
if resetting seen_brct helps in one case but harms other one. Raw
thought, tokenization is a single-"thread" process, this might be just
absurd.
--
Sebastian Gniazdowski
psprint3@xxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author