What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

UpGuard checks and validates configurations for every major OS, network device, and cloud provider.

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Edit all files found having a specific string found by grep

Terminal - Edit all files found having a specific string found by grep
find . -type f -exec grep -qi 'foo' {} \; -print0 | xargs -0 vim
2009-09-03 17:55:26
User: arcege
Functions: find grep xargs
Edit all files found having a specific string found by grep

Make sure that find does not touch anything other than regular files, and handles non-standard characters in filenames while passing to xargs.


There is 1 alternative - vote for the best!

Terminal - Alternatives
grep -Hrli 'foo' * | xargs vim
2009-09-03 15:44:05
User: dere22
Functions: grep xargs
Tags: vim sed awk grep

The grep switches eliminate the need for awk and sed. Modifying vim with -p will show all files in separate tabs, -o in separate vim windows. Just wish it didn't hose my terminal once I exit vim!!

grep -ir 'foo' * | awk '{print $1}' | sed -e 's/://' | xargs vim
2009-09-03 15:12:27
User: elubow
Functions: awk grep sed xargs
Tags: vim sed awk grep

This will drop you into vim to edit all files that contain your grep string.

grep -ir 'foo' * | awk -F '{print $1}' | xargs vim
2009-09-03 15:58:47
User: verboEse
Functions: awk grep xargs
Tags: vim sed awk grep

saves one command. Needs GNU grep though :-(

find . -exec grep foobar /dev/null {} \; | awk -F: '{print $1}' | xargs vi
2009-09-03 16:02:18
User: verboEse
Functions: awk find grep xargs
Tags: vim awk find grep

needs no GNU tools, as far as I see it

Know a better way?

If you can do better, submit your command here.

What others think

doesn't work on native Solaris e.g., as "-print0" is not supported for find, neither is "-0" for xargs.

Comment by verboEse 432 weeks and 2 days ago

In Emacs, it is just `M-x rgrep'.

Comment by ashawley 431 weeks and 2 days ago

This definately works:

grep -l -r "string" | xargs -I {} vi {}

Comment by tusharty 373 weeks and 4 days ago

tusharty, I believe the grep command is missing something. Your command doesn't work on Ubuntu, Redhat, Fedora.

Comment by arcege 373 weeks and 1 day ago

Your point of view

You must be signed in to comment.