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



List files containing given search string recursively

Terminal - List files containing given search string recursively
find /path/to/dir -type f -print0 | xargs -0 grep -l "foo"
2012-06-19 16:27:30
User: apotheos
Functions: find grep xargs
List files containing given search string recursively

Know a better way?

If you can do better, submit your command here.

What others think

or: ag /path

or: ack /path

... or perhaps even more useful:

sag /path

F {N} .. where {N} is the number provided from sag for the match(s) ... and the file opens in $EDITOR

sack /path

F {N} .. where {N} is the number provied from sack for the match(s) ... and the file opens in $EDITOR

... and note by default grep is not desciminate, it will search binary files, whatever is passed to it from find. Both 'ack' and 'ag' have some level of descrimination by default (which of course can be fine tuned).

Comment by khayyam 258 weeks and 5 days ago

the content management munged the above commands! ... there should be a 'string' between command and /path.

Comment by khayyam 258 weeks and 5 days ago

Your point of view

You must be signed in to comment.