Search and Replace across multiple files

grep -lr -e '<oldword>' * | xargs sed -i 's/<oldword>/<newword>/g'
- grep for the word in a files, use recursion (to find files in sub directories), and list only file matches -| xargs passes the results from the grep command to sed -sed -i uses a regular expression (regex) to evaluate the change: s (search) / search word / target word / g (global replace)

By: o0110o
2011-08-27 02:42:51

What Others Think

If you are using grep's -r switch, thus running a recursive search, you can specify the present working directory name instead of the glob * in order to search for all files. That will also search for dot files and will be more efficient. i.e. grep -lr -e '<oldword>' . instead of grep -lr -e '<oldword>' *
RanyAlbeg · 572 weeks and 1 day ago
Also I'd recommend -s -I grep options to skip read access errors and binary files
zolden · 572 weeks ago
Thanks for your input folks :)
o0110o · 569 weeks and 6 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: