this post was submitted on 06 Sep 2024
614 points (90.4% liked)

linuxmemes

21625 readers
90 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    614
    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 3 months ago by LuuTuyen@lemmy.world to c/linuxmemes@lemmy.world
    242 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] FQQD@lemmy.ohaa.xyz 109 points 3 months ago* (last edited 3 months ago) (4 children)

    It's neat that Linux has the ability to do this, but I honestly can't think of a good usecase for this. I think this is more confusing than it is useful

    [–] poinck@lemm.ee 24 points 3 months ago (2 children)

    Git likes to have a word with you.

    [–] Linssiili@sopuli.xyz 39 points 3 months ago* (last edited 3 months ago) (1 children)

    Command 'Git' not found

    [–] Blooper@lemmynsfw.com 4 points 3 months ago

    Beautiful

    [–] wizardbeard@lemmy.dbzer0.com 12 points 3 months ago (1 children)

    Huh, what makes this a use case in favor of case sensitive file names? How does git use this feature?

    [–] OrganicMustard@lemmy.world 26 points 3 months ago (1 children)

    Create multiple branches that only differ in cases from a Unix OS so it breaks git for Windows users in the same project.

    [–] TrickDacy@lemmy.world 9 points 3 months ago

    We had a repo with some really weird (filename) case issues on Mac also. I could only fix it on my home Linux machine, by deleting all the affected files, committing that, then restoring them with all lowercase names. Only time I've dealt with that in 20 years but it can happen!

    [–] gramie@lemmy.ca 9 points 3 months ago (2 children)

    I feel the same way about programming languages. There is no way that "User" and "user" should refer to different variables. How many times has that screwed people up, especially in a weekly typed language?

    One of the many things that I feel modern versions of Pascal got right.

    [–] Serinus@lemmy.world 11 points 3 months ago* (last edited 3 months ago) (2 children)

    Nope. Completely different.

    Case is often used to distinguish scope. Lowercase is local while uppercase is public. "Name = name" is a pretty standard convention, especially in constructors.

    There is a ubiquitous use case in programming. There is not in the file system.

    [–] gramie@lemmy.ca 5 points 3 months ago

    My point is not about how case is meant to be used my point is that it is very easy to make a mistake that is difficult to spot. I think it makes a lot more sense to the case insensitive, and force different names to be used.

    [–] calcopiritus@lemmy.world 3 points 3 months ago

    This is the first time I've seen uppercase denoting scope. Usually it is done with a "_" or "__" prefix.

    Casing styles usually mean different identifier types.

    snake_case or pascalCase for functions and variables, CamelCase for types, UPPER_SNAKE_CASE for constants, and so on.

    If we want to apply this to file systems, you could argue something like: CamelCase for directories, snake_case for files, pascalCase for symlinks, UPPER_SNAKE_CASE for hidden files.

    [–] ArbitraryValue@sh.itjust.works 9 points 3 months ago* (last edited 3 months ago)

    My naming convention for C++ is that custom types are capitalized and instances aren't. So I might write User user;.

    [–] 5714@lemmy.dbzer0.com 1 points 3 months ago (1 children)

    It's quite useful for stuff like PROGRAM and Program in the same directory where PROGRAM is the program itself and Program is some unrelated files about the program. Bad example, but the case stands.

    [–] redisdead@lemmy.world 0 points 3 months ago (1 children)

    So what you're telling me is that it's useful when the software you use is made by absolute idiots?

    [–] 5714@lemmy.dbzer0.com 2 points 3 months ago (1 children)

    It's not about software. Program, PROGRAM were just placeholders for content. I know you can think more abstract and argue in better faith than this.

    [–] redisdead@lemmy.world -1 points 3 months ago

    Replace 'software' by w/et placeholder thing

    [–] Kusimulkku@lemm.ee 0 points 3 months ago

    I think if you can write them in two different ways it should consider them two different things