Timeline for Why does 'find -exec cmd {} +' need to end in '{} +'?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16, 2015 at 9:41 | vote | accept | Martin Tournoij | ||
| Jan 16, 2015 at 1:43 | answer | added | Gilles 'SO- stop being evil' | timeline score: 7 | |
| S Jan 16, 2015 at 0:38 | history | suggested | Scott - Слава Україні | CC BY-SA 3.0 |
Improved formatting (and punctuation); added "history" tag.
|
| Jan 16, 2015 at 0:22 | review | Suggested edits | |||
| S Jan 16, 2015 at 0:38 | |||||
| Jan 15, 2015 at 22:57 | history | edited | Martin Tournoij | CC BY-SA 3.0 |
Add preface since not everyone seems to have read & understood the entire question...
|
| Jan 15, 2015 at 22:56 | history | tweeted | twitter.com/#!/StackUnix/status/555861080254451712 | ||
| Jan 15, 2015 at 22:06 | comment | added | don_crissti |
FWIW, the POSIX page also says that The "-exec ... {} +" syntax adopted was a result of IEEE PASC Interpretation 1003.2 #210 and in that document you'll find more details, e.g.: Note that the "+" is only treated as special if it immediately follows "{}". This minimises the chances of causing problems with existing uses of "+" as an argument with "-exec".
|
|
| Jan 15, 2015 at 21:50 | history | edited | Martin Tournoij | CC BY-SA 3.0 |
added 1 character in body
|
| Jan 15, 2015 at 21:35 | history | asked | Martin Tournoij | CC BY-SA 3.0 |