Might depend on your file browser.
You may also want to try, for example, the files “a1”, “a2”, “a3”, and “a10”. Lexicographically, “a2”>“a10”, but my file browser displays “a10” after “a2”.
Might depend on your file browser.
You may also want to try, for example, the files “a1”, “a2”, “a3”, and “a10”. Lexicographically, “a2”>“a10”, but my file browser displays “a10” after “a2”.
Think the other way around: What’s the use case for case insensitive file names? Does it justify the effort and complexity for the filesystem and the programs to know the difference between lower and upper space chars?
Interesting!
But what about the 16th century judges sentencing people to torture just for a trifle?
Is this based on actual evidence or is it just prejudice?
Upgrading on arch involves looking at the arch news. And IIRC, there was also a warning for some time when upgrading grub. So, assuming people who use arch, btw, use it properly, I don’t see the issue.
I think this is some kind of furry thing.