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.

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:



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.




Redirect STDIN

Terminal - Redirect STDIN
< /path/to/file.txt grep foo
2009-03-29 02:43:40
User: atoponce
Functions: grep
Redirect STDIN

Several times, I find myself hitting my up arrow, and changing the search term. Unfortunately, I find myself wasting too much time typing:

grep kernel /var/log/messages

Redirecting STDIN allows me to put the search term at the end so I less cursor movement to change what I'm searching for:

< /var/log/messages grep kernel

If you're using the emacs keyboard binding, then after you press your up arrow, press CTRL+w to erase the word.

If this has already been submitted, I couldn't find it with the search utility.


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

very nice. I had not thought of that

Comment by GNUix 312 weeks and 4 days ago

This is very nice. I had always used

cat file|grep foo

for easy editing. Good to know there's a better syntax.

Comment by clockworkavian 312 weeks and 4 days ago

grep foo

Comment by jnash 312 weeks and 4 days ago

I wanted to say: grep foo

Comment by jnash 312 weeks and 4 days ago

Oh well.. looks like theres some garbling of comments.

(here goes)

I wanted to say: grep foo "lessthan"(cat file)

Comment by jnash 312 weeks and 4 days ago

clockworkavian: using grep with cat like that is highly discouraged, as it (needlessly) invokes cat. I like the suggestion for redirecting stdin.

Comment by kaedenn 312 weeks and 3 days ago

@kaedenn I know it's discouraged, as grep can do it natively, but for long filenames, having to hit the arrow keys a bunch of times to change a search term is a pain.

I will follow the correct way when it involves less work (the redirection is acceptable), but when it involves more work, I think I'll do it wrong and cut down the RSI

Comment by clockworkavian 312 weeks and 2 days ago

Your point of view

You must be signed in to comment.