Linux

2359 readers

10 users here now

Shit, just linux.

Use this community for anything related to linux for now, if it gets too huge maybe there will be some sort of meme/gaming/shitpost spinoff. Currently though… go nuts

founded 1 year ago

MODERATORS

[email protected]

-1

mv *.jpg is complete bullshit. (sh.itjust.works)

submitted 9 months ago by [email protected] to c/[email protected]

28 comments fedilink hide all child comments

'Well it's only passing mv a list of--' yeah yeah yeah, I know, and that's why I'm calling bullshit. It should be massively harder to execute filenames. Even if 1970s decisions make that the eternal hideous default: the lack of any idiot-proof standard workaround is incomprehensible.

StackOverflow's full of competing one-liners and people pointing out how each one is considered harmful. The least-skeezy options use exec. That sentence should make anyone recoil in horror.

This is not a filename problem. This is a tool problem. If a single printable character is going to silently expand into a list of names, then for god's sake, having it put each name in quotes should be fucking trivial.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 9 months ago (2 children)

What is wrong with mv *.jpg?

[–] [email protected] 3 points 9 months ago

I'm also a bit lost. From the final sentence "having it put each name in quotes should be fucking trivial." OP seems to complain that filenames with spaces expand into multiple arguments. I can't recreate this with this command in bash:

$ printf %s\\n *.jpg

This command prints each argument in its own line. Replace *.jpg with whatever to prove it to yourself. Filenames with spaces show in full in a single line for me.

[–] [email protected] 1 points 9 months ago (2 children)

It expands *.jpg into a list of names.

Which you'd think would mean mv "thing.jpg" "other thing.jpg", but no, it does mv thing.jpg other thing.jpg - and then chokes, because other is not a valid option or filename. Possibly after writing the contents of other thing.jpg onto the destination thing.jpg.

If any filenames contain characters like ; or &, you better hope the next word doesn't look like a command.

[–] [email protected] 5 points 9 months ago

Which shell are you using? This does not happen in Bash, Zsh, or any modern shell I'm familiar with.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

What shell are you using? Is this exclusive to mv (and maybe other builtins)?

Edit: also why would you ever want to move files like this, what is wrong with you

[–] [email protected] -2 points 9 months ago (2 children)

Edit: also why would you ever want to move files like this, what is wrong with you

... like what?

The fuck do you mean, why would I want to move files in a terminal? Because I'm doing shit in a terminal! What, do you expect people to Super+E, find the directory they're in, and drag-and-drop? I'm using tools that only exist in the command line.

I'm using whatever GNOME Terminal came with Linux Mint 20 by default. StackOverflow answers sound like any POSIX terminal will do this. I assume it's standard behavior.

[–] [email protected] 2 points 9 months ago

I’m using whatever GNOME Terminal came with Linux Mint 20 by default.

Should be bash. Type help it should tell you.

StackOverflow answers sound like any POSIX terminal will do this. I assume it’s standard behavior.

Link?

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

I mean with * where you have no control of the order of the files and you never explicitly say which files are being moved. "yeah, just rename files into other files, I don't fucking care lol" is what your command does