From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: "Kamil Jońca" <kjonca@o2.pl>
Cc: zsh-users@zsh.org
Subject: Re: Regexps - what am I doing wrong?
Date: Tue, 8 Mar 2011 01:13:45 -0500 [thread overview]
Message-ID: <20110308061345.GA79682@redoubt.spodhuis.org> (raw)
In-Reply-To: <87ei6ilgcf.fsf@alfa.kjonca>
On 2011-03-07 at 23:24 +0100, Kamil Jońca wrote:
>
> Can somebody explain me why in last line zsh responds "yes"?
> ZSH_VERSION=4.3.10
Bug, introduced by me when I put in the =~ syntax. Fixed for the 4.3.11
release. =~ corrupted parse state in such a way that you only notice it
when followed by &&/|| -- the sense of the following test would be
inverted. Very embarrassing, sorry. The test suite now checks this.
-Phil
next prev parent reply other threads:[~2011-03-08 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 22:24 Kamil Jońca
2011-03-08 6:13 ` Phil Pennock [this message]
2011-03-08 7:09 ` Kamil Jońca
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=20110308061345.GA79682@redoubt.spodhuis.org \
--to=zsh-workers+phil.pennock@spodhuis.org \
--cc=kjonca@o2.pl \
--cc=zsh-users@zsh.org \
/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).