Hellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 28 days agodd: disk destroyerlemmy.caimagemessage-square36fedilinkarrow-up122arrow-down10
arrow-up122arrow-down1imagedd: disk destroyerlemmy.caHellfire103@lemmy.ca to linuxmemes@lemmy.worldEnglish · 28 days agomessage-square36fedilink
minus-squareftbd@feddit.orglinkfedilinkarrow-up5·27 days agoWhat do you mean? Explicitly having to set if= and of= is way harder to screw up than mixing up the order of arguments for e.g. cp.
minus-squareFiskFisk33@startrek.websitelinkfedilinkarrow-up5·26 days agoI could swear the argument order to “ln” swaps every now and then!
minus-squaredebil@lemmy.worldlinkfedilinkarrow-up1·27 days agoUnless you forget what if and of mean. With cp it’s simply “cp what where”. Never had problems remembering that.
minus-squareinsufferableninja@sh.itjust.workslinkfedilinkEnglisharrow-up3·27 days agois it really hard to remember infile and outfile?
minus-squaredebil@lemmy.worldlinkfedilinkarrow-up2·27 days agoNo, but you’re just typing if and of, not infile and outfile, and the letters are right next to each other on a qwerty kbd. One can haphazardly misuse a lot of commands, it’s just that some commands may lead to nastier outcomes than others.
What do you mean? Explicitly having to set
if=andof=is way harder to screw up than mixing up the order of arguments for e.g.cp.I could swear the argument order to “ln” swaps every now and then!
Unless you forget what if and of mean. With
cpit’s simply “cp what where”. Never had problems remembering that.is it really hard to remember infile and outfile?
No, but you’re just typing if and of, not infile and outfile, and the letters are right next to each other on a qwerty kbd. One can haphazardly misuse a lot of commands, it’s just that some commands may lead to nastier outcomes than others.