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

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
11
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.

Alternatives

There is 1 alternative - vote for the best!

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

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 181 weeks and 2 days 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 180 weeks and 5 days ago

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

rm d*<meta-*>

Becomes:

rm dave dog dull

Then you can hit enter, or ctrl-c

Comment by flatcap 180 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts