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.


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

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 while using wildcards

Terminal - prevent accidents while using wildcards
rm *.txt <TAB> <TAB>
2010-11-04 13:58:15
User: boschi
Functions: rm
24
prevent accidents while using wildcards

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

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
echo rm *.txt
2010-10-27 07:26:26
User: alperyilmaz
Functions: echo rm
11

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.

Know a better way?

If you can do better, submit your command here.

What others think

This doesn't seem to be working for me in bash. It works in zsh however. Is there a setting to get it to work in bash?

Comment by Jacolyte 303 weeks and 3 days ago

Not working here either, Bash 4.00

Comment by kovan 303 weeks and 2 days ago

It works for me in 4.0.35. Make sure not to put a space after the txt

Comment by ProfessorTux 303 weeks and 2 days ago

There is something in my bashrc that is preventing it from working, but I don't know what it is (my bashrc has 250 lines).

Comment by kovan 303 weeks and 2 days ago

Your point of view

You must be signed in to comment.