Comment on D or d come on

MonkderZweite@feddit.ch ⁨1⁩ ⁨year⁩ ago

• naught@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  MacOS has a case insensitive file system. It causes me untold grief

  source

  • sysadmin420@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Is a 40 year old it guy, wat

    Macos is case insensitive?!

    source

    • sudo@lemmy.today ⁨1⁩ ⁨year⁩ ago

      OSX offers both case sensitive and case insensitive filesystems

      source

      • naught@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

        Defaults to insensitive and if you want to change it you have to reformat 🥲

        source

        • -> View More Comments
      • sysadmin420@lemmy.world ⁨1⁩ ⁨year⁩ ago

        Wow, I figured it’d be case sensitive, crazy, gotta make it more windows like I guess.

        source
• Honytawk@lemmy.zip ⁨1⁩ ⁨year⁩ ago

  Why would case sensitive path names be considered dangerous?

  source

  • colonial@lemmy.world ⁨1⁩ ⁨year⁩ ago

    I don’t know about dangerous, but case-insensitive Unicode comparison is annoying, expensive and probably prone to footguns compared to a simple byte-for-byte equality check.

    (And yes, all modern filesystems support Unicode. Linux stores them as arbitrary bytes, Apple’s HFS uses… some special bullshit, and Windows uses UTF-16.)

    source

    • lnee@lemm.ee ⁨1⁩ ⁨year⁩ ago

      so if linux stores file names as arbitrary bytes them could I modify a ext4 fs to include a / in a file name

      source

      • kattfisk@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

        If you did it would likely break something as it’s one of only two characters not allowed in a file name (the other being null).

        You can do a lot of funky stuff within the rules though, think about control characters, non-printing characters, newlines, homographs, emojis etc. and go forth and make your file system chaos!

        source
    • MenacingPerson@lemm.ee ⁨1⁩ ⁨year⁩ ago

      Meanwhile fishshell:

      source