Re^3: One-line shell script for find and replace

This simply isn't true. Read the docs.
find ./ | xargs perl -e'print "\n@ARGV"'
Should output one line with all of the arguements sent to perl.

Alternativly, just for the sake of putting this out there, this can be done without xargs
find ./ -exec perl -e'print "\n@ARGV" {} \;
But this would execute numerous copies of perl.

But, fear not! for find has an altnative syntax!
find ./ -exec perl -e'print "\n@ARGV"' {} +
Which is also probably the best way to acomplish this task.

Evan Carroll
www.EvanCarroll.com

Comment on Re^3: One-line shell script for find and replace Select or Download Code

Replies are listed 'Best First'.
Re^4: One-line shell script for find and replace by blazar (Canon) on Oct 05, 2005 at 09:03 UTC
This simply isn't true. Read the docs. `find ./ \| xargs perl -e'print "\n@ARGV"'` Should output one line with all of the arguements sent to perl. You're perfectly right. I knew but just forgot it. Indeed this is the reason why at some time I got used to do stuff like `find . -type f \| while read f; do stuff with $f; done` [download] whenever I suspected that the argument list may have been too long. (Now I generally stick with `-exec`.) Alternativly, just for the sake of putting this out there, this can be done without xargs `find ./ -exec perl -e'print "\n@ARGV" {} \;` But this would execute numerous copies of perl. Indeed. It was me to point this out in the first place, as you can see in the post you're replying to. But fear not for find hsa an altnative syntax! `find ./ -exec perl -e'print "\n@ARGV"' {} +` Which is also probably the best way to acomplish this task. Interesting. This I authentically didn't know. Of course it's all out there in the manpages, I guess. But generally you learn "this kinda things" as people tell you about them...	[reply] [d/l] [select]
Re^5: One-line shell script for find and replace by eyepopslikeamosquito (Archbishop) on Oct 05, 2005 at 13:15 UTC
Of course it's all out there in the manpages, I guess. Well, it's in the recent man pages. ;-) Notice that James Youngman only added -exec {}+ support to GNU findutils on 15 January 2005. Not sure how commonly this handy (and more secure than xargs) find option is implemented on other Unices.	[reply]