this post was submitted on 06 Sep 2024
615 points (90.6% liked)

linuxmemes

20880 readers
8 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
615
Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive (lemmy.world)
submitted 2 months ago by [email protected] to c/[email protected]
237 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 2 months ago (1 children)

They are not created by people. They are created by programs.

[–] [email protected] 1 points 2 months ago (1 children)

what kind of programs are you using that use case in filenames. Smells like a skill issue to me.

[–] [email protected] 1 points 2 months ago (1 children)

Iirc Ubuntu names their home files "Downloads", "Documents", and so on. Same with windows (there are a lot of uppercase letters in windows files). I've had issues with Cargo.toml before. And not just cargo, many config files use case to signal priority (so if both Makefile and makefile exist, Makefile will be used (or other way around)). Downloaded files are a gamble. Files created by user input (so for example if I wanted my user to be "Calcopiritus", my home would be "/home/Calcopiritus".

Uppercase letters might not be common in filenames, but they are not nonexistent.

[–] [email protected] 1 points 2 months ago

by default sure, aren't these just like, XDG specifications or something? Surely you can just change them.

Case in config files is certainly interesting, not sure how i feel about that as a standard.

Downloaded files are a gamble, but they're always a gamble, they might not even be in english lol