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

Remove all files previously extracted from a tar(.gz) file.

Terminal - Remove all files previously extracted from a tar(.gz) file.
tar -tf <file.tar.gz> | xargs rm -r
2009-07-06 22:23:11
User: prayer
Functions: rm tar xargs
38
Remove all files previously extracted from a tar(.gz) file.

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
tar -tf <file.tar.gz> | parallel rm
2010-01-28 08:28:16
Functions: tar
-2

xargs deals badly with special characters (such as space, ' and "). To see the problem try this:

touch important_file

touch 'not important_file'

ls not* | xargs rm

Parallel https://savannah.nongnu.org/projects/parallel/ does not have this problem.

for i in $(tar -tf <file.tar.gz>); do rm $i; done;
2009-07-06 19:57:23
User: din7
Functions: rm tar
-4

Remove annoying improperly packaged files that untar into the incorrect directory.

Example, When you untar and it extracts hundreds of files into the current directory.... bleh.

Know a better way?

If you can do better, submit your command here.

What others think

None of these alternatives is perfect. If one of the tar's directories has other files (like /usr/share/man), the 'rm -r' from alternative 1 will end up erasing the whole directory. And alternative 2 just does not remove directories.

My take:

tar tf <file.tar.gz> | sort -r | while read file; do if [ -d "$file" ]; then rmdir "$file"; else rm -f "$file"; fi; done

--> This command will spit a few error messages if there are already files on some directories, etc., but it will work OK and safe and will erase files and directories in the right order (files first, respective directories afterwards).

Comment by Patola 372 weeks and 2 days ago

many times people use * to build their archives which cause me some time stamp way to do this ... why not interrogate the archive ... Usually *nix users behave and put stuff in a folder then tar it up ... but most of the time when I see * archive it's .zip file ... this this inspired me to come up with this one:

unzip -lt foo.zip | grep testing | awk '{print $2}' | xargs rm -r
Comment by copremesis 372 weeks and 1 day ago

use pipe | while read a; instead of xargs. it happened to me to have too many entry to finish the buffer using xargs

Comment by ioggstream 372 weeks ago

Your point of view

You must be signed in to comment.