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



Delete all files found in directory A from directory B

Terminal - Delete all files found in directory A from directory B
for file in <directory A>/*; do rm <directory B>/`basename $file`; done
2009-05-04 12:44:50
User: jamiebullock
Functions: file rm
Delete all files found in directory A from directory B

This command is useful if you accidentally untar or unzip an archive in a directory and you want to automatically remove the files. Just untar the files again in a subdirectory and then run the above command e.g.

for file in ~/Desktop/temp/*; do rm ~/Desktop/`basename $file`; done


There are 4 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

cd ~/Desktop/temp find * -type f -exec rm ~/Desktop/temp/{} \;
Comment by SlimG 308 weeks and 2 days ago

@SlimG I think you meant the cd to be 'cd ~/Desktop' so in one line it would be:

find directoryA -type f -exec rm directoryB/{} \;

@jamiebullock many times you can replace a bash for loop that does a single action on some set of files with a single find command. Find lets you be very specific about the files you are searching for way beyond common shell "globbing" such as ls *.png, and then specify actions to be taken on each matching file, such as deletion, or running an arbitrary command with each match as the argument. See 'man find' for more.

Comment by bwoodacre 308 weeks and 2 days ago
tar tzf archive.tar.gz | xargs rm
Comment by log0 308 weeks and 1 day ago

@SlimG @bwoodacre Yes i'm also a big fan of find, but I periodically forget to use it! I agree it's cleaner than the for loop.

@log0 That's *very* nice

Comment by jamiebullock 308 weeks ago

@log0 bet me to it but

ls dirA | xargs -I file rm dirB/file

Comment by Newky 146 weeks and 1 day ago

Your point of view

You must be signed in to comment.