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

linuxmemes

21226 readers
86 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!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] 9point6@lemmy.world 43 points 2 months ago (6 children)

    Oh it's even better, windows explorer can't really do case sensitive

    But NTFS is a case sensitive file system

    This occasionally manifests in mind boggling problems

    [–] Wolf314159@startrek.website 14 points 2 months ago (1 children)

    Yeah, it's super weird. I once named a file with mixed case, but one of the letters was the wrong case. Renaming the file didn't work at first. Renaming a file named PAscalCase.txt to PascalCase.txt resulted in no change to the filename. Windows continued to show it as PAscalCase.txt. I had to rename it to something totally different with different characters entirely, then rename it again to get it right.

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

    Renaming it in Explorer does actually rename the file if all you change is the case (in current Windows, at least, see the pedantry below), but whatever mechanism Explorer uses to determine "has this file's name changed" is apparently case insensitive. So it won't refresh the file list. I imagine this is yet another one of those damn fool Windows 95 holdovers, or something.

    You don't have to do any multiple-renaming jiggery pokery. Just press F5 to refresh that Explorer window and magically then it'll show you that the file's name was indeed changed all along.

    [–] Kushan@lemmy.world 6 points 2 months ago (2 children)

    You can enable case sensitivity in windows. It's only disabled by default.

    [–] Scrollone@feddit.it 9 points 2 months ago (1 children)

    I wouldn't do it though. It can only lead to problems, especially with poorly coded programs.

    [–] Kushan@lemmy.world 1 points 2 months ago

    It's generally fine, the vast majority of applications are fine with it, it's mainly the legacy shit that falls over.

    You can also enable it on a per directory basis, and I've yet to encounter a Dev tool that has issues with it. Same for the path limit, you can have long paths enabled too.

    [–] dan@upvote.au 1 points 2 months ago* (last edited 2 months ago)

    Same on MacOS - when you format a drive, you can pick whether it's case sensitive or not.

    [–] lud@lemm.ee 4 points 2 months ago

    NTFS is case insensitive because it's supposed to be more POSIX compatible than its precursors.

    Source: https://learn.microsoft.com/en-us/troubleshoot/windows-client/backup-and-storage/fat-hpfs-and-ntfs-file-systems#posix-support

    [–] stupidcasey@lemmy.world 1 points 2 months ago

    Lol, I have a NTFS drive in a Linux container so I didn’t have to re download everything I had on windows works perfectly fine, now I’m assuming if I ever try to move it back to windows something horrible will break.