Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: [BUG] `$match` is haunting my regex’s trailing, optional, capture

X-seq: zsh-workers 52387
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: chris0e3@xxxxxxxxx
Cc: zsh-workers@xxxxxxx
Subject: Re: [BUG] `$match` is haunting my regex’s trailing, optional, capture
Date: Fri, 8 Dec 2023 22:23:10 -0800
Archived-at: <https://zsh.org/workers/52387>
In-reply-to: <A231AE39-13BE-487E-AE31-AF35F2891A8C@gmail.com>
List-id: <zsh-workers.zsh.org>
References: <A231AE39-13BE-487E-AE31-AF35F2891A8C@gmail.com>

On Fri, Dec 8, 2023 at 9:14 PM <chris0e3@xxxxxxxxx> wrote:
>
>   setopt rematch_pcre
>   [[ 'REQUIRE. OPT' =~ 'REQUIRE.(\s*OPT)?' ]] && printf '\tA. ‹%s›\n' $match
>   [[ 'REQUIRE.'     =~ 'REQUIRE.(\s*OPT)?' ]] && printf '\tB. ‹%s›\n' $match

Aside, you should use e.g. "$match[@]" there (including the quotes) or
you'll be surprised when there is more than one back reference.

> It looks like: if there is a match, but no captures are matched then `$match` is not cleared.

The output of your latter example is certainly not consistent with e.g.

 setopt extendedglob
 [[ 'REQUIRE.' = (#b)REQUIRE.(*OPT)(#c0,1) ]] && printf '\tB. ‹%s›\n' $match

And I can reproduce your example with the most recent git checkout, as
well.  Oliver recently updated to pcre2, so if a patch appears, you
may be on your own to backport it.

Follow-Ups:
- [PATCH?] Re: [BUG] `$match` is haunting my regex’s trailing, optional, capture
  - From: Bart Schaefer

References:
- [BUG] `$match` is haunting my regex’s trailing, optional, capture
  - From: chris0e3

Messages sorted by: Reverse Date, Date, Thread, Author