Timeline for remove spaces in filenames in find output [duplicate]
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 30, 2021 at 17:02 | vote | accept | Stephen Boston | ||
| Jul 30, 2021 at 17:01 | comment | added | Stephen Boston | @ilkkachu Exactly. I thought I was doing that with '{}'. Guess not. I was not trying to remove the spaces. | |
| Jul 30, 2021 at 14:40 | comment | added | ilkkachu | You don't want to remove the spaces if they're part of the filenames. The result would be a different filename. Instead you want to keep the filenames intact, but separate. But the thing is that the shell doesn't make it too easy to do that the way you hope to do it. Some mandatory reading linked. | |
| Jul 30, 2021 at 14:38 | history | duplicates list edited | ilkkachu | duplicates list edited from Why does my shell script choke on whitespace or other special characters?, Why is looping over find's output bad practice? to Why does my shell script choke on whitespace or other special characters?, Why is looping over find's output bad practice?, Understanding the -exec option of `find` | |
| Jul 30, 2021 at 14:37 | history | duplicates list edited | ilkkachu | duplicates list edited from Why is looping over find's output bad practice? to Why does my shell script choke on whitespace or other special characters?, Why is looping over find's output bad practice? | |
| Jul 30, 2021 at 14:37 | answer | added | AdminBee | timeline score: 2 | |
| Jul 30, 2021 at 14:37 | history | closed | ilkkachu bash Users with the bash badge or a synonym can single-handedly close bash questions as duplicates and reopen them as needed. | Duplicate of Why is looping over find's output bad practice? | |
| Jul 30, 2021 at 14:30 | history | asked | Stephen Boston | CC BY-SA 4.0 |