Hacker News Reader

Comment by floatingatoll | Hacker News Reader

While not an alternative, please bugfix your bash:

mv "$@" ~/.Trash/

Even simpler:

  alias del="mv -t ~/.Trash/"

Now let's delete them after roughtly 30 days:

  alias del="mv -t ~/.Trash/ ; find ~/.Trash/ -mtime +30 -exec rm {} \;"

This is not fine, as deleting a small file can be very long if there's a large file to be deleted in the trash.

Yeah running the delete in the user's crontab (i.e. in the background and on a schedule) would be a better option IMO.

This fails on directories, as the -r switch was not included:

    mkdir foo; del foo

and including it will spawn file not found errors for the contents of the foo directory, if any.

EDIT: See also neighbor comment about appending filenames!

This does not work. The arguments to `del` get appended at the end, after `find`. You want this:

  del() { mv "$@" ~/.Trash/ && find ~/.Trash -mtime +30 -delete }

I also replaced the unnecessary exec by find's builtin -delete

Thank you, it's painful to see people providing replacements for critical commands like `rm` without understanding basic shell features like aliases.

And just a reminder everybody please don't run random scripts you find on the internet.

P.S. you need a semicolon before the close brace :)

Correct me if I'm wrong, but wouldn't that instantly delete all moved files which are older than 30 days since mv keeps the mtime?

You’re not wrong :)

This fails on non-GNU mv(1) binaries such as macOS.

Thanks for pointing out! Now everyone’s Bashing me in their comments.

I love how OP's "safe" rm can lead to data loss.

How so?

By moving files to ~/.Trash you didn't expect, which would be deleted when you empty ~/.Trash.