Hi, I'd like to forward a bug filled by Gunnar Wolf in Debian some time ago:
"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, Santiago
