From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20429 invoked by alias); 3 Apr 2017 01:29:00 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22651 Received: (qmail 5828 invoked from network); 3 Apr 2017 01:29:00 -0000 X-Qmail-Scanner-Diagnostics: from mx.spodhuis.org by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(94.142.241.89):SA:0(-2.3/5.0):. Processed in 1.087861 secs); 03 Apr 2017 01:29:00 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED, RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,T_DKIM_INVALID,UNPARSEABLE_RELAY autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: zsh-workers+phil.pennock@spodhuis.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at spodhuis.org designates 94.142.241.89 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201702; h=In-Reply-To:Content-Type:MIME-Version:References :Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding :Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=uC+sAUxrqk9SMCq9UGqbEtd/GH06rmAbomJwZuF9sHc=; b=Sp6UyjTSw8wFwwmyZyExLiUzd3 KpBCvJXJWc+CkWofUHC7fM5FOtuG6oc3GpraFXND/etY6oDcSrmOyNglCkRBOTzHBGurS+HHNXHxb NmDGkbnQX8fbEFcxb+zKeOLnexdHXw4NuXsldV5xH6dxG7KeJMrFHc/KPoBTwWzzQkllHy3Tyvfa3 9aMHa/RJRozlREPBfgiQ/3Gefk2J; Date: Mon, 3 Apr 2017 01:12:00 +0000 From: Phil Pennock To: Bart Schaefer Cc: zsh-users@zsh.org Subject: Re: REMATCH_PCRE with zsh built without pcre support Message-ID: <20170403011159.GA64116@tower.spodhuis.org> References: <27c2026c-f760-32b0-e0d5-8c6909346979@gmx.com> <170401145348.ZM30308@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <170401145348.ZM30308@torch.brasslantern.com> OpenPGP: url=https://www.security.spodhuis.org/PGP/keys/0x4D1E900E14C1CC04.asc 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. Perl introduced the syntax and I originally wrote the Zsh =~ code to use the existing zsh/pcre module. It was only reluctantly that I added the zsh/regex module so that =~ could match Bash's behavior by default, because folks felt that compatibility with Bash was more important than being powerful. Almost everything I do with =~ in Zsh uses REMATCH_PCRE. > 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. -Phil