• FrostyPolicy@suppo.fi
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 month ago

      On Linux file systems you can use any character except NULL, and / is a reserved character.

      E.g. on ext-4 “All characters and character sequences permitted, except for NULL (‘\0’), ‘/’, and the special file names “.” and “…” which are reserved for indicating (respectively) current and parent directories.”

      • CanadaPlus@lemmy.sdf.org
        link
        fedilink
        arrow-up
        0
        ·
        1 month ago

        So … is allowed, or all whitespace, or Zalgo text.

        I mean, on the one hand, I guess why be restrictive, but on the other I feel like requiring something that looks like language somehow might be a good idea to avoid edge cases and attacks.

        • unalivejoy@lemmy.zip
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 month ago

          You can have new lines in your file names. YSAP has a good video/playlist about how to deal with these and many more.

      • xthexder@l.sw0.com
        link
        fedilink
        arrow-up
        0
        ·
        1 month ago

        I once accidentally created a file with a newline character in it… it was pretty tricky to fix from command line.

        • Warl0k3@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          1 month ago

          Did you not just use tab? That’s the usual method of dealing with weird characters in filenames that I’ve found

          • xthexder@l.sw0.com
            link
            fedilink
            arrow-up
            0
            ·
            1 month ago

            This was quite a while ago now, but I don’t think my shell escaped the tab complete properly, I remember it just printing a literal newline and evaluating it as a second command. I think there was other unicode in there too, otherwise I would have just typed it out. I had to do something with null terminated output and piping it in to mv, but I can’t remember what exactly.

    • Gyroplast@pawb.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      In filenames? AMATEURS! Use obscure Unicode in your passphrases for maximum security. Ctrl-Shift-U, enter arbitrary code point, bam! 🦊 Works even better with a Compose key and a nice, chonky .XCompose file to throw some gr∑∑k letters around, for instance, like some confused script kiddie. :)

      On topic: There are multiple variants of spaces in Unicode. You’re welcome, and now go and create something utterly deranged with that information.

  • lemming741@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    Microsoft intentionally made programs install to C:\Program Files on Windows 95+ to force programmers to deal with spaces in filenames.

    Someone make one of those “statements made by the utterly deranged” memes about it, please and thank you.

  • asdfranger@lemmynsfw.com
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 month ago
    Oh\ come\ on,\ it\'s\ not\ that\ bad
    

    Some shells enclose those types of files within inverted commas. Such that:

    > ls
    file\ name.md
    

    is instead

    > ls
    'file name.md'
    

    (I use fish)

          • Revan343@lemmy.ca
            link
            fedilink
            arrow-up
            0
            ·
            1 month ago

            On its own, the backtick is primarily used in computing, and so doesn’t have an old-timey-English name, nor does the Jargon File mention a Commonwealth Hackish name for it. While there are a variety of other names, I don’t think any of them are specific to the UK

            When used with a letter, it marks a grave accent; this was its original purpose on a typewriter