Hide

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.


If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

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.

Universal configuration monitoring and system of record for IT.
Hide

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:

Hide

News

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!
Hide

Top Tags

Hide

Functions

Hide

Credits

Search for a <pattern> string inside all files in the current directory

Terminal - Search for a <pattern> string inside all files in the current directory
find . -type f -exec grep -i <pattern> \;
2009-09-22 14:06:11
User: levenbrech
Functions: find grep
1
Search for a <pattern> string inside all files in the current directory

shorter typing with no need to use xargs.

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
grep -RnisI <pattern> *
2009-09-22 15:09:43
User: birnam
Functions: grep
Tags: bash grep
42

This is how I typically grep. -R recurse into subdirectories, -n show line numbers of matches, -i ignore case, -s suppress "doesn't exist" and "can't read" messages, -I ignore binary files (technically, process them as having no matches, important for showing inverted results with -v)

I have grep aliased to "grep --color=auto" as well, but that's a matter of formatting not function.

grep -r <pattern> * .[!.]*
2009-09-22 14:57:40
User: danam
Functions: grep
3

Searches all files,dirs (also hidden) recursively

find . -type f -print0 | xargs -0 grep -i <pattern>
ack <pattern>
2009-09-22 14:08:34
User: levenbrech
1

ack seeks for , list all found files and display everything in nice colors. Look for it in http://betterthangrep.com/

grep -nisI <pattern> * .[!.]*
2013-04-18 14:33:41
User: lajarre
Functions: grep
0

options: -n line nbrs, -i ignore case, -s no "doesn't exist", -I ignore binary

args: * for all files of current dir (not hidden), .[!.]* for all hidden files

I don't include by default the -R (recursive) option, which is not always useful. You add it by hand when needed.

Know a better way?

If you can do better, submit your command here.

What others think

you forgot the braces. Should be:

find . -type f -exec grep -i <pattern> {} \;
Comment by sharfah 306 weeks ago

You may find that using xargs (or changing to find's "xargs mode" with -exec {} +) will be faster if you are grepping very many files though because it invokes grep as few times as possible.

Comment by bwoodacre 306 weeks ago

Your point of view

You must be signed in to comment.