31 ms·
Well, I think just about all of my filenames have personal names in them - they tend to start with /home/geofft. And "never," your original claim, is not "hard
by geofft 8y ago
Well, I think just about all of my filenames have personal names in them - they tend to start with /home/geofft.
And "never," your original claim, is not "hardly ever," your revised claim. If there are valid use cases for case-sensitive filenames, it seems like it should be allowed on robustness-principle grounds, even if they are rare, unless they impose some disproportionate cost on users of the system.
And filenames don't have to be in English, and usually aren't. "geofft" is not an English word; neither is "usr" or "etc" or "tmp," let alone "xt_RATEEST.h" or "/tmp/tmp.CGZ8Lq5f".
And even for common nouns in English, case matters - the UCC for instance requires certain text to be "conspicuous," and gives one example as "a heading in capitals equal to or greater in size than the surrounding text." It's pretty common for lawyers to write "conspicuous" text in all caps to satisfy this requirement. In these cases, you do want to distinguish between "never," "Never," and "NEVER".
- lisper 8y agoNothing prevents you from having file names that mix cases in a case-insensitive file system. Case-insenstitive is not the same as case-oblivious. For example: $ echo asdf > Foo $ cat foo asdf That's much less error prone that allowing you to have distinct files named foo and Foo and FOO and FoO and fOo and fOO and...