2 ms·
Another common rename is the three way: mv file file.bak; mv file.new file Nested {} can handle that one, cutting four 'file's down to one: eval mv file{
by tzs 7y ago
Another common rename is the three way:
mv file file.bak; mv file.new file
Nested {} can handle that one, cutting four 'file's down to one:
eval mv file{,{.bak\;mv\ ,.new},}
Anyone have a way to hack that to cut the two 'mv's down to one?
- JadeNB 7y agoI didn't know {} could nest!
- CraneWorm 7y agoIt sorta can't... note the use of eval.
- tzs 7y agoThe eval isn't to help with the nesting. The {} stuff nests just fine, as we can see by changing the "eval mv" to printf: $ printf '[%s]' file{,{.bak\;mv,.new},} [file][file.bak;mv][file.new][file] (Note: I took out the '\ ' from the original because I realized it is not necessary). The eval is there because in bash text expansion occurs after ';' is interpreted, and we need that to be the other way around. Hence, the escaping of ';' in the input to preserve it for text expansion, and then the eval afterward to get ';' interpreted.
- CraneWorm 7y agoSorry, I should have checked. I jumped at it because there are other things one might like to achieve with brace expansion but turn out to be impossible because it is evaluated first - you can't use them with variables.
- TheDong 7y ago> Anyone have a way to hack that to cut the two 'mv's down to one? Yup: mv -bS .bak file{.new,} Should give the same result if you're using gnu coreutils 'mv', though it's obviously not as generally useful as nested braces.