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:



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!

Top Tags



a trash function for bash

Terminal - a trash function for bash
trash <file>
2009-11-25 16:45:15
a trash function for bash

Every rm'ed a file you needed? Of course you haven't. But I have. I got sick of it so I created a bash function. Here it is. It'll put trashed files into a $HOME/.Trash/"date" folder according to the date. I have rm aliased to it as well in my bashrc so that I still use the rm command. It'll choke if you attempt to trash a directory if that directory name is already in the Trash. This rarely happens in my case but it's easy enough to add another test and to mv the old dir if necessary.

function trash(){

if [ -z "$*" ] ; then

echo "Usage: trash filename"


DATE=$( date +%F )

[ -d "${HOME}/.Trash/${DATE}" ] || mkdir -p ${HOME}/.Trash/${DATE}

for FILE in $@ ; do

mv "${FILE}" "${HOME}/.Trash/${DATE}"

echo "${FILE} trashed!"





There are 15 alternatives - vote for the best!

Terminal - Alternatives
trash-put junkfolder
2014-03-09 00:24:09
User: Sepero
Tags: trash

apt-get install trash-cli

Commandline program that allows you put folders or files in the standard KDE/Unity desktop trash.

Know a better way?

If you can do better, submit your command here.

What others think

wouldn't ever use it personally, but I can see how it would be helpful to certain other folks who require the utility this provides.

Comment by linuxrawkstar 348 weeks ago

can this be merged with nautilus' trash folder?

Comment by alperyilmaz 348 weeks ago

@alperyilmaz i don't know. not sure if Nautilus adds metadata when you use Nautilus to trash something. I don't use a DE or X ( I ssh into a server to perform chemistry research ) so there's no way for me to test that.

Comment by thebillywayne 348 weeks ago

I often use this instead of rm:

mv $DELME /tmp

If you have enough disk, it will be deleted in due time.

Comment by susannakaukinen 348 weeks ago

There are many analogs of this command, like a app-misc/perltrash in Gentoo or trash-cli in Debian

Comment by kapsh 347 weeks and 6 days ago

You should quote your variables in case you want to trash a file that has spaces in its name. Also, the "usage" message could be a little more informative.

Comment by dennisw 347 weeks ago

@dennisw: for some reason commandlinefu chopping off when it orginially read "Usage: trash ". also, I don't think $@ can be put in quotations because then $@ will be seen as only one argument. best practice is simply not to use whitespace in filenames; it leads to too much drama.

Comment by thebillywayne 347 weeks ago

dangit! it did it again! putting stuff in brackets must be seen as html or something, because it keeps on getting erased.

Comment by thebillywayne 347 weeks ago

Your point of view

You must be signed in to comment.