4 ms·
This is used to really confuse me too, but now I can't remember why, because everything's the same: touch <destination...> $EDITOR <destination...> mv <c
by OJFord 7y ago
This is used to really confuse me too, but now I can't remember why, because everything's the same:
touch <destination...>
$EDITOR <destination...>
mv <current...> <destination>
cp <current...> <destination>
scp <current...> <destination>
mount <current> <destination>
The place you're putting something is last in each case; we can even include everything that doesn't modify its location.
All I can think of that breaks the rule is `rm`, `unlink`, and `umount`. But they're hardly gotchas, and they're not reversing arguments they just don't have a 'destination'.
- meow1032 7y agoI think "zip" breaks this rule.
- efreak 7y agoThat's because with zip (and tar, and other archivers) you can have multiple items to move to a destination archive. You can also do that with cp and mv if you need to, using `-t`. `cp -t .dotfiles/ .nanorc .bash*`. Generally more useful when you want to move a bunch of files around.
- OJFord 7y agoThe `...` in my post above was to indicate that. Zip does indeed break the 'rule', but this is not an excuse, cp and mv manage just fine with: in in in in [...] out Which is why I said the 'last' rather than 'second'.
- hibbelig 7y agoZip is a DOS tool, so I’m not so surprised it’s not following Unix conventions...