From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8440 invoked by alias); 11 Aug 2017 02:11:39 -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: 22812 Received: (qmail 8345 invoked by uid 1010); 11 Aug 2017 02:11:39 -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 3.117217 secs); 11 Aug 2017 02:11:39 -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=ham 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: | DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201708; 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=9XERTFucU1PkFzeJgDIBjrfNI/5s0a4VpUYrbixrCEI=; b=eaVyRzlW85vrxAt1A7mx4fpc0A paIteYHbOwmulK+27JDBngbECeIGM7Xu6jV9+FJVU0aE+FvZIN8k9DAVWnS9HSNCLMAPIwz87tP3O C6zSVpRkJfy2gtVmBteg2+EOQ8fn7+z0P0OAJ4/L6mUsDr4/5hL/7O7ctBN7IBKoPzgdJD3aKzXbj 9xJCL7nc/2Vmang5je3GW3jaYLU3; Date: Thu, 10 Aug 2017 22:11:22 -0400 From: Phil Pennock To: nimaje+zml@bureaucracy.de Cc: zsh-users@zsh.org Subject: Re: -pcre-match doesn't work since version 5.4.1 Message-ID: <20170811021122.GA95804@tower.spodhuis.org> References: <86221c7e-aa71-28a7-21c2-8ed800090edd@bureaucracy.de> <20170811010701.GA94571@tower.spodhuis.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170811010701.GA94571@tower.spodhuis.org> OpenPGP: url=https://www.security.spodhuis.org/PGP/keys/0x4D1E900E14C1CC04.asc On 2017-08-10 at 21:07 -0400, Phil Pennock wrote: > On 2017-08-11 at 00:29 +0200, nimaje+zml@bureaucracy.de wrote: > > after upgrading to version 5.4.1 I noticed that using -pcre-match doesn't > > work > I see this too; none of the loadable infix operators seem to be working, > so it's not specific to the PCRE module. -regex-match doesn't work > either. I took this to -workers and a patch has been posted. A change in tokenization logic accidentally broke lookup of conditionals where there's a dash inside the conditional name. No idea whether my patch or something else will be applied, but know that what we have includes a regression test so that this one won't slip through again. > As a workaround, `setopt re_match_pcre` and then using =~ as the > operator does still work. (This is why I didn't immediately see the > breakage myself). That workaround applies still. And now we know why it works. :) -Phil