Bug#623241: different grep behavior on x86 vs amd64

2011-06-30 Thread Raoul Bhatia [IPAX]
On 06/29/2011 09:18 PM, Nicolas Bonifas wrote: >> Quoting from the man page: >> >> "Within a bracket expression, a range expression consists of two >> characters separated by a hyphen. It matches any single character that >> sorts between the two characters, inclusive, using the locale's >> collat

Bug#623241: different grep behavior on x86 vs amd64

2011-06-29 Thread Nicolas Bonifas
Hello, >> echo '1303141571.M26770P15859.m01S=1884W=1934:2S' | egrep '[A-Z]$' --color > --> red colored S at the end > >> echo '1303141571.M26770P15859.m01S=1884W=1934:2S' | egrep '[a-z]$' --color > --> grep matches the string but there is no color > > can you explain that too? Quoting from the

Bug#623241: different grep behavior on x86 vs amd64

2011-06-11 Thread Nicolas Bonifas
Hello, Depending on your locale, [a-z] may or may not match uppercase characters. This explains the difference between your computers (which, by the way, are both amd64). This bug report is invalid. Nicolas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subjec

Bug#623241: different grep behavior on x86 vs amd64

2011-04-18 Thread Raoul Bhatia [IPAX]
Package: grep Version: 2.6.3-3 Severity: important hi, i notice grep behaving differently on x86 vs. amd64: on x86, grep works correctly: > raoul@raoul ~ $ echo '1303141571.M26770P15859.m01S=1884W=1934:2S' | egrep > '[a-z]$' ^ no match because there is no [a-z] at the end of the line! > raoul@r