From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-45053-ml=inbox.vuxu.org@zsh.org>
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 a0c0df4e
	for <ml@inbox.vuxu.org>;
	Mon, 16 Dec 2019 21:11:01 +0000 (UTC)
Received: (qmail 27490 invoked by alias); 16 Dec 2019 21:10:52 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
X-Seq: 45053
Received: (qmail 5981 invoked by uid 1010); 16 Dec 2019 21:10:52 -0000
X-Qmail-Scanner-Diagnostics: from mail-wr1-f52.google.com by f.primenet.com.au (envelope-from <stephane.chazelas@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.102.1/25663. spamassassin: 3.4.2.  
 Clear:RC:0(209.85.221.52):SA:0(-2.0/5.0):. 
 Processed in 1.470107 secs); 16 Dec 2019 21:10:52 -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.52 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
         :mime-version:content-disposition:user-agent;
        bh=p3dnu+unemK1Nhst3XulS4td140sSUMqOOTe/e9d3Es=;
        b=EVxrbDZ3M8CpUrRnjMHEqqgBlUAUAhnZxiNC5xS2cC+ShZ1tIB+fMfBqZgG8wbrvjv
         6+FFcEtrRZ6ISPwwUFfzHQLoxC51PjSMjxG/5BqwYWSlQes2tToJJ+nIkh571vdlIrVC
         mKtcXuffO6NL+6WSXbem6mU+PbxnSPgtnBdttnVmxNTUeBkpt8yr52OyTUS78Do1LOVV
         VXmIocX/BckOPIkg+TYJX0gOBTHEz6Q8kyQmZ8B0tygRmOrDu5rdPfSeRhsJ0HIVtDdE
         l1ZVQ9a3b7G+6AH7Kt80N3jfk5Y+oFtWZuzeHxOnxfzyuRPPj2/886r4JNPi7H+lc4jR
         TFkw==
X-Gm-Message-State: APjAAAUEsWimAluNrODNloVf3+wkdQz/Fq+8G1LvaJJ6S8s3nqfzNpVv
	ZyFT3q5kNmiMYGBh0d8Gn6SeEHNM
X-Google-Smtp-Source: APXvYqwAElvFOKJgqYyWy8Ud4AYVmRrz6aIA3o0vbyqfq5m6ZnnpueSFhcMsSaM3556QECQPyv1FhA==
X-Received: by 2002:a5d:4f8e:: with SMTP id d14mr33982817wru.112.1576530615773;
        Mon, 16 Dec 2019 13:10:15 -0800 (PST)
Date: Mon, 16 Dec 2019 21:10:13 +0000
From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: regexp-replace and ^, word boundary or look-behind operators
Message-ID: <20191216211013.6opkv5sy4wvp3yn2@chaz.gmail.com>
Mail-Followup-To: Zsh hackers list <zsh-workers@zsh.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: NeoMutt/20180716

The way regexp-replace works means that these things:

$ a='aaab'; regexp-replace a '^a' x; echo "$a"
xxxb
$ a='abab'; regexp-replace a '\<ab' '<$MATCH>'; echo $a
<ab><ab>
$ set -o rematchpcre
$ a=xxx; regexp-replace a '(?<!x)x' y; echo $a
yyy

don't work properly as after the first substitution, the regex
is no longer matched on the full subject, but on the part of
subject after the last match.

I don't think that can be fixed without exposing more of the
regex/pcre C API.

-- 
Stephane