|
|
xargs and working with spaces in filenames
You can also use the -exec or -execdir option to find:
Incidentally, is egrep the same as "grep -E"? Looks like it. Why does that bother me? ;-)
Rob
xargs and working with spaces in filenames
Yes, egrep is the same as "grep -E"; this is historical, grep was the original command, followed by fgrep ("fast grep") that was very quick but doesn't grok wildcards, and egrep ("enhanced grep") that understood full regular expressions. Later on, these three programs were folded back into one (with 3 hardlinks to the same executable), then the "-E" and "-F" options were added.
xargs and working with spaces in filenames
One of the points in the original post (and indeed the title!) - is working with *spaces* in filenames. Your example should have quotes around the {}
xargs and working with spaces in filenames
Actually, no. Quotes on the command line are only to get around the shell's default command line processing. Whether or not you put quotes around {}, the argument that <tt>find</tt> gets will not have quotes. And it doesn't need them, as the command will not be reinterpreted by any more shells (where quoting might matter), it'll get fork'd and exec'd directly from find with no further processing of the arguments. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|