Timeline for Having some trouble using "find -exec {} +"
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2014 at 18:33 | comment | added | Lii | My man page on -exec comman {} + states Only one instance of {}' is allowed within the command.` but nothing about where {} should be placed. But when testing the command it does require that I place {} in the end. Weird. | |
| Jun 11, 2013 at 20:36 | comment | added | Stéphane Chazelas | There's no spaces coming into the picture there. {} is replaced with a list of arguments passed to the command, that's all. spaces in shell command line are used to separate argument to commands, but here, find doesn't start any shell. | |
| Jun 11, 2013 at 20:26 | comment | added | Hauke Laging | If there is not a language problem (and I misunderstand you) then you are not stating what is. This is: "Because of a design decision {} must come at the end." You say (in my understanding): "Because {} expands to many files {} must come at the end. And that is simply not true. | |
| Jun 11, 2013 at 20:03 | comment | added | bahamat | @HaukeLaging: Take it up with the authors. I am simply stating what is. | |
| Jun 11, 2013 at 20:00 | comment | added | Hauke Laging | That is not a valid argument. There is no technical reason which forbids trailing arguments. The command line calculation would be nearly the same. The only reason is that this is a stupid limitation of both find and xargs. | |
| Jun 11, 2013 at 19:43 | history | answered | bahamat | CC BY-SA 3.0 |