*** This bug is a duplicate of bug 120687 ***
https://bugs.launchpad.net/bugs/120687
Yep, this is a duplicate of that bug. Thanks for finding that.
** This bug has been marked a duplicate of bug 120687
Caseless collate sequence in en_GB.UTF8
--
bash character ranges have unexpected behav
This looks to be the same as bug #120687. Should we mark this as a
duplicate?
--
bash character ranges have unexpected behavior with certain locales
https://bugs.launchpad.net/bugs/571958
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Follow-up, comparing two other systems:
RHEL 5.5 with bash 3.2.25 has the same behaviour as Ubuntu: if LC_ALL is
NOT set then it defaults to locale settings where [a-z] is case-
insensitive.
On Solaris 10 with bash 3.00.16 this is NOT the behaviour. It behaves as
if LC_ALL=C, i.e. case-sensitive.
> "The Unix command-line is case-sensitive" is a maxim of everyday
> Unix practice, and the current configuration is in blatant violation
> of that long-standing convention.
I understand what you're saying, but it's not really in violation of
that principle. bash is still doing everything case-se
Yeah, let us know if other systems handle this better. Thanks.
** Summary changed:
- bash always globs case-insensitively
+ bash character ranges have unexpected behavior with certain locales
** Changed in: bash (Ubuntu)
Status: Incomplete => New
--
bash character ranges have unexpected
