Timeline for Batch rename folders with a single bash command
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 14:16 | history | edited | CommunityBot | Commonmark migration | |
| Apr 13, 2017 at 12:37 | history | edited | CommunityBot | replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/ | |
| Oct 27, 2016 at 23:45 | comment | added | Wildcard | @Gilles, look again. The OP's command prints a mv command with the needed double quotes. | |
| Oct 27, 2016 at 23:43 | comment | added | Gilles 'SO- stop being evil' | Given that the sample names in the question contain spaces, I'd just delete this answer. I'd hardly ever condone piping file names into a shell, but if it's going to fail for the very example in the question, that's a clear no. | |
| Oct 27, 2016 at 23:32 | comment | added | Wildcard | (Actually, I would love to merge this with my other answer; is there a way to do that or should I just delete my other answer and edit the text from it into this one?) | |
| Oct 27, 2016 at 23:31 | comment | added | Wildcard | @Gilles, trust me, I know that. I guess my original answer didn't have enough dire warnings in it, though. How is it now? | |
| Oct 27, 2016 at 23:30 | history | edited | Wildcard | CC BY-SA 3.0 | added 1394 characters in body |
| Oct 27, 2016 at 22:41 | comment | added | Gilles 'SO- stop being evil' | Appending |bash won't work if there are special characters in file names such as spaces. You can make it work, but it's a lot more complicated than simple find usage. | |
| Oct 26, 2016 at 2:38 | history | answered | Wildcard | CC BY-SA 3.0 |