• cally [he/they]@pawb.socialEnglish
    8·
    1 小时前

    not sure why the default behavior is this:

    file\ name\ with\ a\ bunch\ of\ spaces

    instead of this:

    "file name with a bunch of spaces"

    but you can just press " before pressing tab to auto-complete, and it will use the 2nd form

    • rumba@lemmy.zipEnglish
      2·
      1 小时前

      agreed, “still worth it”

      I do, however, tend to keep spaces out of my folder names so i can just use quotes at the end.

      /Images/Halloween/Projections/“Creepy Crawlies.mp4”

      • Gamma@programming.devEnglish
        1·
        1 小时前

        Single quotes don’t allow any escaping in shell, you need

        'I don'\''t know what you mean, I'\''ve never encountered any annoyances'

        Or, in Zsh with setopt rcquotes:

        'I don''t know what you mean, I''ve never encountered any annoyances'
  • notarobot@lemmy.zip
    8·
    12 小时前

    Don’t try svelte kit. This is pseudocode but it’s valid. The only symbol show here that is not real is the / that I’ve placed at the end of folder to show that they are folders. There are other special cases

    routes/
+page.ts
(admin)/
  +page.ts
  [user=uuid]/
    [[community]]/
      +page.ts
    posts/
      [...postIds@]/
        +page.ts
  • jbk@discuss.tchncs.de
    81·
    14 小时前

    smells like skill issue tbh

    tools which cant handle being installed/run on directories with spaces are so annoying

      • ulterno@programming.devEnglish
        1·
        9 小时前

        I vaguely remember zsh in Manjaro (by default) having a tab completion that automatically added the slashes.
        Never set it up myself though.

        But I really hate having to worry about quoting my file variables in scripts.
        So much, that after a certain complexity, I just give up the script and make the thing in C++.

        Oh, and if I make a script that doesn’t handle file names properly (because it’s not required in that specific use case), I make sure to delete it after use, to prevent mistaken use later, which would otherwise cause more headache than just having to rewrite a script.

  • lemming741@lemmy.worldEnglish
    175·
    1 天前

    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.

    • FrostyPolicy@suppo.fi
      71·
      1 天前

      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.”

      • xthexder@l.sw0.com
        51·
        1 天前

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

        • lad@programming.devEnglish
          5·
          17 小时前

          I created a file with backspace in name, it was hard to understand why filename doesn’t match

        • GenderNeutralBro@lemmy.sdf.orgEnglish
          12·
          1 天前

          I actually did this a lot on classic Mac OS. Intentionally.

          The reason was that you could put a carriage return as the first character of a file, and it would sort above everything else by name while otherwise being invisible. You just had to copy the carriage return from a text editor and then paste it into the rename field in the Finder.

          Since OS X / macOS can still read classic Mac HFS+ volumes, you can indeed still have carriage returns in file names on modern Macs. I don’t think you can create them on modern macOS, though. At least not in the Finder or with common Terminal commands.

        • toynbee@lemmy.world
          4·
          1 天前

          I don’t conduct interviews very often, but when I do, one of my questions is always about interacting with files that have special characters in the filename.

        • Warl0k3@lemmy.world
          3·
          1 天前

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

          • Hupf@feddit.org
            1·
            18 小时前

            Too bad when there’s multiple files starting with and consisting mostly of e.g. kanji (when on a Latin keyboard).

          • xthexder@l.sw0.com
            3·
            1 天前

            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.

      • CanadaPlus@lemmy.sdf.org
        6·
        1 天前

        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.

        • Hupf@feddit.org
          2·
          18 小时前

          could you have .​.? I assume most terminals would just spell out .\x200b.?

          • CanadaPlus@lemmy.sdf.org
            1·
            8 小时前

            Or use a hair space so it looks almost the same. Or … but you’ve added the right-to-left unicode character. I’m guessing there’s something that looks a lot like a period, too.

            If ext4 doesn’t include restrictions terminals probably should.

        • unalivejoy@lemmy.zipEnglish
          12·
          1 天前

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

    • nialv7@lemmy.world
      17·
      1 天前

      unix filenames are just string of bytes, the operating system does not interpret it in anyway. this is a much saner approach compared to Windows where language settings can change file system behavior.

      • who@feddit.orgEnglish
        4·
        1 天前

        the operating system does not interpret it in anyway.

        *in any_way. ;)

    • Gyroplast@pawb.socialEnglish
      22·
      1 天前

      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.

      • wizardbeard@lemmy.dbzer0.comEnglish
        8·
        1 天前

        I already deal far too much with trying to handle dumb fucking typos in employee data, and trying to turn human names into valid email addresses.

        The first time I encounter something like this there will be a body. It will not be found.

    • 9point6@lemmy.world
      3·
      23 小时前

      It’s all just Unicode

      You can have emoji as your WiFi network name too

      Kinda interesting to see what older devices do when faced with such a network

    • bigfondue@lemmy.world
      5·
      13 小时前

      You can, but I downloaded some music the other day and I was trying to put the files onto my phone using KDE Connect, and I couldn’t understand why is wasn’t working until I got rid of the star emoji in the filenames. So I think Graphene/Android might still struggle with it.

      • Iced Raktajino@startrek.website
        1·
        1 天前

        Lol, I think that’s how I learned it was possible, too. yt-dlp uses the title as the filename, and all of the emojis came along with it. Was trying to rename them from terminal, but couldn’t do much when half the filenames started with the fire emoji lol.

    • TootSweet@lemmy.worldEnglish
      7·
      1 天前

      10 seconds of googling indicates this is true for Windows and Mac as well. I haven’t looked specifically, but I’d be a little surprised if it wasn’t true for Android and iOS as well.

      But really, why would they add rules to prevent people from using certain unicode codepoints in filenames? Should they disallow Klingon as well? Kanji? Of course not. Emojis are codepoints just like U+0061 is.

      Of course there are good reasons to disallow things like newlines and forward slashes in Linux filenames, but what specifically would even be the argument for preventing emojis?

  • katy ✨@piefed.blahaj.zoneEnglish
    21·
    1 天前

    the struggle between spaces in filenames look cute and oh fuck what’s the code to reference a space in a filename in terminal?

  • asdfranger@lemmynsfw.com
    38·
    1 天前
    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
            4·
            1 天前

            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

        • Luc@lemmy.world
          2·
          1 天前

          In dutch I’ve heard them be called flying commas unapologetically (vliegende comma’s — ironically has one in it because many plurals need it, it doesn’t mark possession)