@#5: yes, the (buried) documentation states that the "preferred" way is to not assume that char ranges are case-sensitive (apparently SuSv3 also recommends this), but the fact remains that Unix users have, for 30+ years, been relying on case-insensitive ranges. Bash behaves differently on some systems when LC_ALL is _unset_. Some systems i've tested (RHEL + Ubuntu) treat an _unset_ LC_ALL as a case-insensitive locale, whereas others (e.g. Solaris and some Linuxes) treat it equivalently to LC_ALL=C. The latter behaviour is "historically correct."
i was hit by this in the same manner as the original reporter, nuking 30GB of home directories when i did: mv home HOME rm -fr [a-z]* before cleaning up a drive for a new Ubuntu installation (full details are in #571958). -- Caseless collate sequence in en_GB.UTF8 https://bugs.launchpad.net/bugs/120687 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
