this post was submitted on 18 Nov 2023
567 points (95.8% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54424 readers
372 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] adespoton@lemmy.ca 20 points 11 months ago (2 children)

“\ “ 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 9 points 11 months ago (2 children)

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 14 points 11 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 11 points 11 months ago* (last edited 11 months ago) (2 children)

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/

[–] PoolloverNathan@programming.dev 1 points 11 months ago* (last edited 11 months ago) (1 children)

Does SSH require quoting commands?

[–] gears@sh.itjust.works 1 points 11 months ago (1 children)

It doesn't for commands without spaces (i.e reboot) You might be able to escape the spaces and not use quotes, I'm not sure

[–] PoolloverNathan@programming.dev 1 points 11 months ago

Might be client-dependent; I've regularly ran commands with spaces (e.g. ssh a@a.local ssh b@b.local) without a problem.

[–] LocustOfControl@reddthat.com 1 points 11 months ago

Yup, this is me with scp. Well, it would be if I didn't just use asterisks to avoid that PITA.

[–] cobra89@beehaw.org 4 points 11 months ago (1 children)

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 6 points 11 months ago

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