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.

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:



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



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

prevent accidents and test your command with echo

Terminal - prevent accidents and test your command with echo
echo rm *.txt
2010-10-27 07:26:26
User: alperyilmaz
Functions: echo rm
prevent accidents and test your command with echo

if you're using wildcards * or ? in your command, and if you're deleting, moving multiple files, it's always safe to see how those wildcards will expand. if you put "echo" in front of your command, the expanded form of your command will be printed. It's better safe than sorry.


There are 3 alternatives - vote for the best!

Terminal - Alternatives
rm *.txt <TAB> <TAB>
2010-11-04 13:58:15
User: boschi
Functions: rm

alternative for "echo rm *.txt". Just doubletab the command you are willing to use and it will show you the affected files.

Know a better way?

If you can do better, submit your command here.

What others think

nice idea.. a good default way to test parameter expansion if your inputrc doesn't auto-expand already.

Comment by AskApache 312 weeks and 1 day ago

In terms of preventing some rm-related accidents, you may also want to install safe-rm: http://www.safe-rm.org.nz

On Debian/Ubuntu:

apt-get install safe-rm
Comment by fmarier 311 weeks and 4 days ago

If you hit Meta-* (usually Alt+Shift+8), then inputrc will expand all the wildcards inline. e.g.

rm d*<meta-*>


rm dave dog dull

Then you can hit enter, or ctrl-c

Comment by flatcap 311 weeks and 4 days ago

Your point of view

You must be signed in to comment.