• Em Adespoton
    link
    fedilink
    English
    arrow-up
    31
    arrow-down
    8
    ·
    7 months ago

    “\ “ and [tab] and * are your friends. I’ve been using spaces in Unix filesystems since the early 90s with no issues. Also, using terminal fonts that•put•a•faint•dot•in•each•space•character helps.

    • ShaunaTheDead@kbin.social
      link
      fedilink
      arrow-up
      10
      arrow-down
      1
      ·
      7 months ago

      Yeah, either put quotes around it ‘/like this/you can incorporate/spaces/into your paths’ or /just\ escape/your\ spaces/like\ this

      • silasmariner@programming.dev
        link
        fedilink
        English
        arrow-up
        15
        arrow-down
        1
        ·
        7 months ago

        This is fine for the most basic of use cases but once you start looping through file names or what have you, you have to start writing robust correct bash and nobody does that

      • gears@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        11
        ·
        edit-2
        7 months ago

        It gets real crazy when you’re sending remote commands so you have to escape the escapes so that the remote keeps them and properly escapes the space

        ssh -t remote "mv /home/me/folder\\\ with \\\ spaces /home/me/downloads/

    • cobra89@beehaw.org
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      7 months ago

      Yeah but at least with periods in the title tab complete will just complete the file name all the way while with a filename with spaces I have to escape the damn space with "\ " like you said. Why do more work when I don’t have to?

      • Euphoma@lemmy.ml
        link
        fedilink
        English
        arrow-up
        6
        ·
        7 months ago

        My shell seems to autocomplete filenames that have spaces with "\ " already.