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

grep certain file types recursively

Terminal - grep certain file types recursively
find . -name "*.[ch]" -exec grep "TODO" {} +
2009-08-13 06:17:22
User: peshay
Functions: find grep
3
grep certain file types recursively

-exec works better and faster then using a pipe

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
grep -r --include="*.[ch]" pattern .
2009-08-13 01:41:12
User: sitaram
Functions: grep
Tags: grep
10

doesn't do case-insensitive filenames like iname but otherwise likely to be faster

find . -name "*.[ch]" | xargs grep "TODO"
grep -r --include=*.php "something" /foo/bar
2014-03-07 13:26:12
User: avpod2
Functions: grep
0

Actually grep can do recursive search based on file extensions.

Know a better way?

If you can do better, submit your command here.

What others think

it would seem so yes, but it's really much closer to a tie here. In -exec {} + mode find invokes as many grep instances as xargs does, and the pipe has little overhead. What you really want is a recursive grep as originally posted by sitaram:

grep -r --include="*.[ch]" TODO .
Comment by bwoodacre 267 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts