GNU bug report logs - #78940
REGEX wrongfully matches pattern

Previous Next

Package: sed;

Reported by: "Duchesne, Alexandre" <duchesne.alexandre.3 <at> courrier.uqam.ca>

Date: Wed, 2 Jul 2025 05:43:03 UTC

Severity: normal

Done: Jim Meyering <jim <at> meyering.net>

Bug is archived. No further changes may be made.

Full log


Message #13 received at 78940-done <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Davide Brini <dave_br <at> gmx.com>
Cc: 78940-done <at> debbugs.gnu.org
Subject: Re: bug#78940: REGEX wrongfully matches pattern
Date: Thu, 3 Jul 2025 10:03:54 -0700
tags 78940 notabug
close 78940
stop

On Wed, Jul 2, 2025 at 6:27 AM Davide Brini via <bug-sed <at> gnu.org> wrote:
> On Tue, 1 Jul 2025 20:26:16 +0000, "Duchesne, Alexandre"
> <duchesne.alexandre.3 <at> courrier.uqam.ca> wrote:
>
> > Hi,
> >
> > I wanted to show to my classmate the comportment of a RegEX using sed to
> > capture the subgroup in a pattern match.
> >
> > But, when trying with sed -E, the pattern matched even though it should
> > not have.
> >
> > Can someone explain to me why if this comportment turns out to be normal ?
> >
> > View snippet :
> >
> > $ echo abc | grep -E '(...).+' -c
> > 0
> > $ echo abc | sed -E 's/(...).+/\1/'
> > abc
>
> This is all expected behavior. Your regexp does not match, no sostitution
> is performed, and sed prints the input line unchanged, which is the default
> behavior (disable with sed -n).

Thanks for replying. I've marked this issue as resolved and "not a bug".




This bug report was last modified 49 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.