[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problem with pathname expansion
|
From: |
Chris Down |
|
Subject: |
Re: problem with pathname expansion |
|
Date: |
Fri, 27 Dec 2013 11:23:11 +0800 |
|
User-agent: |
Mutt/1.5.22 (2013-10-16) |
On 2013-12-27 07:16:12 +0400, vollitwr . wrote:
> Thank you very much. You had explainded the problem. However it does
> not remove it. :-( It is not bug according to documentation. But it
> is the pure formality only. It looks like deep and conceptual error
> beyond scope of the bash developers.
Yes, the locales are part of (g)libc, not bash. I personally would not
consider it a bug, just non-intuitive behaviour for people who expect
ASCII (but I would hesistate to construe that as "it is non-intuitive
to everyone" -- I don't think that's the case. Certainly I don't find it
totally unsurprising).
> It is obvious that letters 'b' and 'B' are different for everybody in
> any locale
Danger Will Robinson!
> but pattern [A-C] ignores this and nocasematch option. :-( I can only
> hope that one day the better concept will be used and this well
> fortified bug will be removed... How is it possible to use sequence
> like aAbBcC... for the range patterns?!
As stated by Greg, use a POSIX or C locale when doing collation.
LC_COLLATE=C should do what you want.
pgp1v2dc7imSk.pgp
Description: PGP signature