Thanks for the info (and for the bug renaming - i fired it off before experimenting enough to determine the culprit), but i still consider this to be a bug in the default Ubuntu configuration. Scripts copied from other platforms (even other Linuxes) are ticking time-bombs.
i'm using the default LC config, and my system is set up for US/English, so it should (as far as i'm aware) be behaving like the C locale as far as collation is.concerned. step...@jareth:~$ env | grep LC step...@jareth:~$ If i explicitly set it to 'C' then it works as it should: step...@jareth:~$ export LC_ALL=C step...@jareth:~$ ls -d [A-Z]* Desktop Public Documents ... Regardless of what SUSv3 specifies, i have never worked on a Solaris/Linux/BSD system (or programming language) which had case-insensitive character ranges. This just bit me in the ass big-time. i have verified that it happens on my 9.10 box as well, and it's a miracle i haven't nuked huge amounts of data already, as i _instinctively_ rely on all Unix shell operations being case-sensitive (and very often make use of that). -- bash always globs case-insensitively https://bugs.launchpad.net/bugs/571958 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
