bug#60618: closed (unicode characters are not identified as such for \w and \b with -P)

[GNU bug Tracking System]

Your message dated Sat, 7 Jan 2023 18:28:49 -0800
with message-id 
<CA+8g5KFxt_SKL=tMPbRMnZhojv522x--OY-iq4k0SQpuTcfuQQ@mail.gmail.com>
and subject line Re: bug#60618: unicode characters are not identified as such 
for \w and \b with -P
has caused the debbugs.gnu.org bug report #60618,
regarding unicode characters are not identified as such for \w and \b with -P
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
60618: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60618
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: unicode characters are not identified as such for \w and \b with -P Date: Fri, 6 Jan 2023 19:48:01 -0800

Reported to PCRE[1] with mention of GNU grep being also affected.

[1] https://github.com/PCRE2Project/pcre2/issues/185

0001-pcre-use-UCP-in-UTF-mode.patch
Description: Text Data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#60618: unicode characters are not identified as such for \w and \b with -P
>
>
>
>
> Date: 
>
> Sat, 7 Jan 2023 18:28:49 -0800
>
>
>
>
> On Fri, Jan 6, 2023 at 11:37 PM Jim Meyering <jim@meyering.net> wrote:
> > On Fri, Jan 6, 2023 at 11:28 PM Jim Meyering <jim@meyering.net> wrote:
> > > On Fri, Jan 6, 2023 at 7:49 PM Carlo Arenas <carenas@gmail.com> wrote:
> > > > Reported to PCRE[1] with mention of GNU grep being also affected.
> > > >
> > > > [1] https://github.com/PCRE2Project/pcre2/issues/185
> > >
> > > Yikes. This is a big deal.
> > > Thank you for the patch and added test.
>
> I've also added the new names to THANKS.in and pushed this:
> https://git.savannah.gnu.org/cgit/grep.git/commit/?id=5e3b760f65f13856e5717e5b9d935f5b4a615be3
>
>
> --- End Message ---