From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id a1b44249 for ; Tue, 17 Dec 2019 07:39:30 +0000 (UTC) Received: (qmail 9898 invoked by alias); 17 Dec 2019 07:39:25 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 45062 Received: (qmail 27207 invoked by uid 1010); 17 Dec 2019 07:39:25 -0000 X-Qmail-Scanner-Diagnostics: from mail-wr1-f48.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25663. spamassassin: 3.4.2. Clear:RC:0(209.85.221.48):SA:0(-2.0/5.0):. Processed in 2.451954 secs); 17 Dec 2019 07:39:25 -0000 X-Envelope-From: stephane.chazelas@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.221.48 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=uvCeq8yIuU1waX6cQuunCyCQVcZCJa0tg/d/fkqngq0=; b=tz6Y0MxzHwu2w46NV+UxUiGH3FOXo9gtXohvBbywk7G6yPRWnfrzkPII777ZolNTgG kpMINmzSKUr3dZ75GUCEXCeGNEAAgz+qsNfeXWmTId4oci0+rZbFKRNBj6SFCegfbMQ4 QRkEPTM+wFlp1owNIMAWB64o+Yr5ax+wJk04cUtfvJffK/QvE3VfQI3OSzZSN6ZuzaGk 0KupjVEpJTSNySHG7V7UU+ezr8oAHxHWLNPoIDFd+mSt0HU9dJM35BgfO1Zt39XVZcnE 4xzTXRUiaWXCbbx8KcyetCpLVflSrCQv0rE8dpDD30R9yv6SbUjV7a3hS0Ss+2dvkfTL m3cQ== X-Gm-Message-State: APjAAAU1GDXS48wmyHL7HyxJgJSOcB1hSI2/+NMD5LUxblJp8JBr1lof cEhJWDJKLxuiCxAiWoHNoj390ENH X-Google-Smtp-Source: APXvYqyubfPZqxLuftmPJJ6EUikTbcuuiXgnHCouFQ6g1Mi6Xb6LkutyAqJhXgiezG2xx8pY58SMpQ== X-Received: by 2002:a5d:6748:: with SMTP id l8mr36132212wrw.188.1576568328746; Mon, 16 Dec 2019 23:38:48 -0800 (PST) Date: Tue, 17 Dec 2019 07:38:46 +0000 From: Stephane Chazelas To: Zsh hackers list Subject: Re: regexp-replace and ^, word boundary or look-behind operators Message-ID: <20191217073846.4usg2hnsk66bhqvl@chaz.gmail.com> Mail-Followup-To: Zsh hackers list References: <20191216211013.6opkv5sy4wvp3yn2@chaz.gmail.com> <20191216212706.i3xvf6hn5h3jwkjh@chaz.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191216212706.i3xvf6hn5h3jwkjh@chaz.gmail.com> User-Agent: NeoMutt/20180716 2019-12-16 21:27:06 +0000, Stephane Chazelas: [...] > PCRE should be OK, so it could be just a matter of > exposing it via the pcre_match builtin [...] D'oh, it's there already with the -b, -n options. I'll try and suggest a regexp-replace improvement using that. -- Stephane