Timeline for I HATE spaces in file names
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 12, 2014 at 7:48 | comment | added | M.Herzkamp | This works, and I said in the challenge that the appendix is up to you. +1 | |
| Aug 8, 2014 at 23:14 | history | edited | Etan Reisner | CC BY-SA 3.0 |
added 198 characters in body
|
| Aug 8, 2014 at 22:53 | comment | added | pqnet |
When collision happen on directory names, it will put one into another (and not strip spaces). Use -T option to mv to avoid this
|
|
| Aug 8, 2014 at 19:33 | history | edited | Etan Reisner | CC BY-SA 3.0 |
Included improvements suggested by Dennis.
|
| Aug 8, 2014 at 19:30 | comment | added | Etan Reisner |
@Dennis Yeah. I saw the -d conversation on pqnet's answer but figured since I was silencing the mv screaming I'd avoid the find screaming. Though I should probably shorten it for the screaming one. And yeah, I always quote {} for some reason even though I know you don't have to in this case. Force of habit I guess.
|
|
| Aug 8, 2014 at 19:21 | comment | added | Dennis |
You can use -d instead of -depth and you don't need the quotes around {}.
|
|
| Aug 8, 2014 at 15:46 | review | First posts | |||
| Aug 8, 2014 at 16:24 | |||||
| Aug 8, 2014 at 15:42 | history | answered | Etan Reisner | CC BY-SA 3.0 |