Zsh Mailing List Archive
Messages sorted by:
Re: REMATCH_PCRE with zsh built without pcre support
- X-seq: zsh-users 22652
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh Users <zsh-users@xxxxxxx>
- Subject: Re: REMATCH_PCRE with zsh built without pcre support
- Date: Mon, 3 Apr 2017 00:13:00 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Tih4zg8D0EHLWiVres0AZ5gZpCxd1XcJKdcD0rIW6cg=; b=awwO2T8d7MBl7l+G5sjNFETR6Rk7wTyI3LTn8WOqLZK8yYCe24bjhM6vFLLNGV6pxv sbaAW7TFpQn7+aACG0aDRpjIdWbrb7Y3UsPTIrkWh1UsDyc0KrKKC6RbP4fU9AfhEH3R EfBaqgwROZNLaVgt/oY1pp5OYM4TwMN7G79ky4fjcxCZLp29Opu8PSe6qYwbV7jhzED0 kMf6HiYJ4XOg9QleQ+bOPEb1r3FU3oYw1bLXVXDjUTMX6Jg31nqdqxhoQfE38HzroM+D Il+e2w0hCcKqXujsuFk2y/D0DUsqAcmoBUQDLgfl/Kfc3c1qYIt4akpJ5tCXAC/wwi86 Sqvg==
- In-reply-to: <20170403011159.GA64116@tower.spodhuis.org>
- List-help: <mailto:email@example.com>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <email@example.com> <170401145348.ZM30308@torch.brasslantern.com> <20170403011159.GA64116@tower.spodhuis.org>
On Sun, Apr 2, 2017 at 6:12 PM, Phil Pennock
> On 2017-04-01 at 14:53 -0700, Bart Schaefer wrote:
>> I'd personally be more inclined to do away with REMATCH_PCRE and that
>> =~ special-case entirely, and require explicit use of the -pcre-match
>> operator (or a shorter equivalent) when you want those semantics.
> That's a shame.
To clarify, I'm not advocating any such demotion of PCRE. However,
*IF* the presence of the option when the module is not available is
really a serious problem, then I think the right thing is to remove
the option, rather than to expand the special case.
>> It's already been pointed out in another thread that =~ doesn't work at
>> all if the shell is built with the default modules and without dynamic
>> linking support.
> I'll have to hunt down that thread and see what I can do about that.
It's the recent "zregexparse" thread where this came up. I'm not sure
there is anything to be done about it; the zsh/regex module would have
to become part of the default static build, which might have licensing
Messages sorted by: