From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Another minor =~ glitch
Date: Fri, 7 Apr 2017 10:33:20 -0700 [thread overview]
Message-ID: <170407103320.ZM27783@torch.brasslantern.com> (raw)
Side note to the REMATCH_PCRE thread: xtrace output shows what's being
done, but it can't be "played back":
torch% set -x
torch% [[ foo =~ .* ]]
+Src/zsh:2> [[ foo -regex-match .* ]]
torch% [[ foo -regex-match .* ]]
+Src/zsh:3> [[zsh: unknown condition: -regex-match
]]
torch%
next reply other threads:[~2017-04-07 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 17:33 Bart Schaefer [this message]
2017-04-08 1:58 ` Roland Eggner
2017-04-08 5:23 ` Bart Schaefer
2017-06-14 4:45 ` Mikael Magnusson
2017-06-14 4:49 ` Mikael Magnusson
2017-06-19 10:06 ` PATCH: dupstring a possibly readonly string before modifying Mikael Magnusson
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=170407103320.ZM27783@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).