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.

Top Tags



Unarchive entire folder

Terminal - Unarchive entire folder
for f in *;do case "$(echo $f|sed "s/.*\.\([a-z\.]*\)/\1/g")" in zip)unzip -qqo $f&&rm $f;;tar.gz|tar.bz2)tar xf $f&&rm $f;;rar)unrar e -o+ -r -y $f&&rm $f;;7z)7z e -qqo $f;;esac;done
2009-08-17 03:50:50
User: matthewbauer
Unarchive entire folder

This will unarchive the entire working directory. Good for torrents (I don't know why they put each file into a seperate archive).


There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

for file in *;do case "$(echo $file|sed "s/.*\.\([a-z\.]*\)/\1/g")" in tar.gz)tar xfz $file&&rm $file;;zip)unzip -qqo $file&&rm $file;;tar)tar xf $file&&rm $file;;tar.bz2)tar yxf $file&&rm $file;;rar)unrar e -o+ -r -y $file&&rm $file;;7z)7z e -qqo $file;;esac;done

for 7z files (i was just over the 255 character limit)

Comment by matthewbauer 296 weeks and 1 day ago

then change $file -> $f to shorten it! :-) You use it 13 times.

Comment by bwoodacre 296 weeks ago

oh yeah, and recent versions of tar will automatically uncompress .gz or .bz2 files (when they have the extension) so you only need one case to handle them:

case "$(echo ... )" in tar.gz|tar.bz2) tar xf $f && rm $f;;

this looks like a good candidate for a function save into ~/.bashrc, just put the command text inside the {}:

function unarchive_folder () { COMMANDS_HERE; }

and append it to your ~/.bashrc

Comment by bwoodacre 296 weeks ago

Your point of view

You must be signed in to comment.