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 complex regexes. To illustrate the point:
$ echo | egrep -v '[[:digit]]+' egrep: Unmatched [ or [^ The brackets _are_ balanced, however the character class is not (it lacks a finishing colon). Thanks, -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-vserver-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages grep depends on: ii libc6 2.9-7 GNU C Library: Shared libraries grep recommends no packages. Versions of packages grep suggests: ii libpcre3 7.8-2 Perl 5 Compatible Regular Expressi -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
