Timeline for Recursively rename all the files without changing their extensions?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2023 at 7:17 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | need to make sure file names contain at least one `.` (2 for hidden ones). With -exec {} +, we can report errors in the overall exit status and that's more efficient |
| Oct 23, 2018 at 17:04 | comment | added | don_crissti | @tjt263 - the benefit is explained in the link in my comment. I don't have anything to add, really... Feel free to not use it but then, as I said, you'll have to adjust the parameters accordingly... | |
| Oct 23, 2018 at 17:03 | comment | added | voices | @don_crissti Well, my question to you is, why bother/what's the point? It makes a complicated command line slightly more complicated, with no benefit that I can see. I'm happy to be corrected though. | |
| Oct 20, 2018 at 19:52 | comment | added | don_crissti | @tjt263 - why ? Yes, you can but then you have to change $1s to $0s... See What does the x in "find ... -exec sh -c '...' x {}" mean? | |
| Oct 20, 2018 at 19:50 | comment | added | voices | Can it be omitted? | |
| Oct 20, 2018 at 19:19 | comment | added | user232326 | @tjt263 The "second sh" is not a command, it is the name of the shell started by sh -c, change it to findsh if you wish. | |
| Oct 20, 2018 at 19:18 | comment | added | user232326 | This -exec {} \; calls a new shell per each file found | |
| Oct 20, 2018 at 18:59 | comment | added | voices | What's the second sh for? | |
| Oct 20, 2018 at 17:02 | history | edited | don_crissti | CC BY-SA 4.0 | added 175 characters in body |
| Oct 20, 2018 at 16:44 | history | answered | don_crissti | CC BY-SA 4.0 |