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

by Skeeve (Parson)

on Oct 05, 2005 at 07:53 UTC ( [id://497511]=note: print w/replies, xml )

Need Help??

No need for the / after the .
You forgot to put a \ in front of *
If you don't put it there your find will fail as soon as you have *.txt files in the current directory because the shell will replace "*.txt" by a list of those files.

So:

perl -pi -w -e 's/find/replace/g' `find . -name \*.txt`
[download]

OTOH: I prefer to use xargs for situations like this, just because the command line usually has limits.

find . -name \*.txt -print0 | xargs -0 perl -pi -w -e 's/find/replace/
+g'
[download]

$\=~s;s*.*;q^|D9JYJ^^qq^\//\\\///^;ex;print

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

Replies are listed 'Best First'.
Re^3: One-line shell script for find and replace by ruoso (Curate) on Oct 05, 2005 at 18:17 UTC
I still prefer: `find . -name '*.txt' -exec perl -pi -e 's/find/replace/g' {} \;` [download] daniel	[reply] [d/l]
Re^4: One-line shell script for find and replace by Anonymous Monk on Oct 05, 2005 at 20:17 UTC
In the prior solution, you execute the perl interpreter once. In yours, you execute it many times. You gain maybe a little clarity, but you lose on performance. Only pointing this out if you have 10k files to deal w/	[reply]

Domain Nodelet^?

Node Status^?

node history
Node Type: note [id://497511]
help

Chatterbox^?

How do I use this? • Last hour • Other CB clients

Other Users^?

Others avoiding work at the Monastery: (3)

As of 2024-04-24 23:10 GMT

Sections^?

Information^?

Find Nodes^?

Leftovers^?

Voting Booth^?

No recent polls found