Bug#525213: grep: Misleading error message when presenting a badly formed character class

2016-02-29 Thread santiagorr
control: clone -1 -2 control: retitle -2 "regex: fix [ diagnostic" control: reassign -2 glibc control: tags -2 + patch control: block -1 -2 El 26/02/16 a las 08:49, Jim Meyering escribió: > On Fri, Feb 26, 2016 at 6:51 AM, wrote: > > Hi, > > > > I'd like to forward a bug

Bug#525213: grep: Misleading error message when presenting a badly formed character class

2009-04-22 Thread Gunnar Wolf
Package: grep Version: 2.5.4-4 Severity: normal It seems that whenever egrep finds something it cannot digest inside a character class, it spews out the same error string: «Unmatched [ or [^». This can be misleading and opens the way for long debugging time, specially when trying to understand