Timeline for Change filename from lowercase to uppercase recursively
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 27, 2013 at 4:23 | vote | accept | hd. | ||
| Jul 25, 2013 at 11:18 | comment | added | Gilles 'SO- stop being evil' |
@Ameer rename will never be called with an argument of the form dir.xyz/abc.txt, because -execdir was used and not -exec. All the arguments to rename will be of the form ./SOMETHING where SOMETHING doesn't contain any slash. So dir.xyz will be renamed to DIR.xyz, which is consistent with the expressed requirements. Thanks to -depth, this happens after dir.xyz/abc.txt has been renamed to dir.xyz/ABC.txt, so there won't be a problem with find attempting to move into a directory that's been renamed without it knowing.
|
|
| Jul 25, 2013 at 5:21 | comment | added | msw |
It is ambiguous in the OP whether files or {files and directories} were to be changed. I read -type f and Giles infers the opposite. We're both wrong and both right.
|
|
| Jul 25, 2013 at 5:00 | comment | added | Priya | The above command fails on directory name with a dot(.) separator. ex : dir.xyz/abc.txt is being renamed to DIR.xyz/ABC.txt | |
| Jul 25, 2013 at 1:59 | history | answered | Gilles 'SO- stop being evil' | CC BY-SA 3.0 |