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.

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

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

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 -print0 | xargs -0 grep -i <pattern>
2009-09-22 13:31:23
User: xelon
Functions: find grep xargs
2
Search for a <pattern> string inside all files in the current directory

Alternatives

There are 2 alternatives - vote for the best!

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

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 -exec grep -i <pattern> \;
2009-09-22 14:06:11
User: levenbrech
Functions: find grep
1

shorter typing with no need to use xargs.

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.

Your point of view

You must be signed in to comment.

Related sites and podcasts