5 ms·
OK, so renaming a file should be: $ mv new-name.txt old-name.txt I defer to the blogger's superior UX expertise!
by kazinator 2y ago
OK, so renaming a file should be:
$ mv new-name.txt old-name.txt
I defer to the blogger's superior UX expertise!
- bmacho 2y agoIMO there shouldn't be a way to run programs without named arguments.
- jimbobthrowawy 2y agoHave you ever programmed in objectivec or swift? I imagine what you're describing working something like that, but on the command line. A few years back, mpv changed to make named arguments require an equals rather than a whitespace. I've gotten used to it, but it seems like such a weird outlier.
- im3w1l 2y agoWell consider consistency. In assembly's case. Using to from order makes it consistent with C. Consistent with manuals. And in the case of arithmetic instructions, consistent with the order used in mathematical notation. On the other hand for shell scripts, using from to makes it more consistent. With what? Pipelines read a from-file process it and then write. from to.
- kazinator 2y agoIronically, to from order makes it consistent with memcpy/memmove. But that ISO C function came from AT&T Unix. BSD has bcopy which uses "AT&T syntax".
- suzzer99 2y agoHey it works for github pull requests: base <- compare Merge the right into the left. Sure, totally intuitive.
- tmtvl 2y agoEh, there's examples of every permutation: ;; Lisp (setf a (xor b c)) ;; Kanren ;; Unification instead of mutation. ;; Therefore these are equivalent: (== a (xor b c)) (== (xor b c) a) # Contrived untested Raku example $b ^^ $c ==> my $a; % Amberjack b xor c -> a // Java var a = b ^ c;
- librasteve 2y agotests the raku... my $b = 42; my $c = False; $b ^^ $c ==> my $a; say $a; #[42] ^^ yep
- layer8 2y agonew-name.txt := old-name.txt
- rep_lodsb 2y agoThere are other operating systems that did use something like "ren new-name.txt=old-name.txt". Also, memcpy(dest,source,len) in C.