From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: REMATCH_PCRE with zsh built without pcre support
Date: Tue, 4 Apr 2017 16:00:13 -0700 [thread overview]
Message-ID: <170404160013.ZM17829@torch.brasslantern.com> (raw)
In-Reply-To: <e023fb5e-c841-210a-5d94-837d3141a580@eastlink.ca>
On Apr 4, 8:22am, Ray Andrews wrote:
} Subject: Re: REMATCH_PCRE with zsh built without pcre support
}
} Pardon, I don't understand the details of any of this, but would not the
} above be setting a time-bomb? Surely it should be explicit which method
There would have to be an explicit "zmodload zsh/pcre" somewhere in order
for the pcre semantics to apply.
This is a little worse than REMATCH_PCRE because the option could be
toggled with LOCAL_OPTIONS whereas other special handling would be
needed to use the module only within a certain function scope. That's
why I asked whether there were any known cases that would break.
But if you use =~ at all, you're accepting that *some* regex module
is going to be loaded. If PCRE is a strict superset, you don't need
to care *what* module -- unless you want to use superset features, in
which case you'd better "zmodload zsh/pcre" yourself anyway.
next prev parent reply other threads:[~2017-04-04 23:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 19:09 Eric Cook
2017-04-01 21:53 ` Bart Schaefer
2017-04-03 1:12 ` Phil Pennock
2017-04-03 7:13 ` Bart Schaefer
2017-04-03 11:26 ` Daniel Shahaf
2017-04-03 18:00 ` Bart Schaefer
2017-04-04 0:36 ` Daniel Shahaf
2017-04-04 2:43 ` Bart Schaefer
2017-04-04 12:27 ` Eric Cook
2017-04-05 13:08 ` Daniel Shahaf
2017-04-04 15:22 ` Ray Andrews
2017-04-04 23:00 ` Bart Schaefer [this message]
2017-04-05 13:42 ` Peter Stephenson
2017-04-05 22:28 ` 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=170404160013.ZM17829@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).