Bug#930247: grep: inconsistent behaviour with anchored regex containing back-references

2023-01-20 Thread Santiago Ruano Rincón
Control: -1 -2 Control: retitle -1 grep: inconsistent behaviour with anchored regex containing back-references Control: severity -1 normal Control: found -2 3.4-1 Control: notfound -2 2.27-2 On Fri, 02 Dec 2022 02:12:20 +0100 Thorsten Glaser wrote: > Package: grep > Version: 3.6-1 > Followup-For

Bug#930247: grep: inconsistent behaviour with anchored regex containing back-references

2022-12-01 Thread Thorsten Glaser
Package: grep Version: 3.6-1 Followup-For: Bug #930247 X-Debbugs-Cc: t...@mirbsd.de Control: found 930247 3.8-3 Control: severity 930247 serious Control: retitle 930247 grep: does not handle backreferences correctly, violating POSIX I’m running into this, in stable and unstable both: (sid-amd64)

Bug#930247: grep: inconsistent behaviour with anchored regex containing back-references

2019-06-10 Thread Santiago Ruano Rincón
Control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36148 Control: tags -1 + upstream Thanks for your bug report, -- Santiago El 09/06/19 a las 11:22, g1 escribió: > Package: grep > Version: 2.27-2 > Severity: normal > > There seems to be a problem with beginning/end-of-line an

Bug#930247: grep: inconsistent behaviour with anchored regex containing back-references

2019-06-09 Thread g1
Package: grep Version: 2.27-2 Severity: normal There seems to be a problem with beginning/end-of-line anchors in regex containing back-references: $ cat words ana deed ill stats Using -x to match whole line works: $ egrep -x '(.?)(.?).?\2\1' words ana deed stats Using explicit anchors emits fa