3 ms·
I've never once used `trash-put`, but thanks for introducing it to me. Personally I've never found the concept of a temporary storage area for files I want to d
by imiric 5y ago
I've never once used `trash-put`, but thanks for introducing it to me. Personally I've never found the concept of a temporary storage area for files I want to delete to be helpful. Even on Windows I would Shift-Delete files to skip the step of having to review it later. And in most cases I would just empty the Recycle Bin without checking.
The thing is that many Linux commands can wreck your system if you're not careful: a wrong `dd` or `mkfs`, removing a core package and its dependencies, a wrong change in `/boot`, etc.
I've definitely lost work because of this, but it always served as a learning experience, and I was more careful next time. I don't think I'd want to use a system with training wheels, not even when I was learning. The whole idea of Unix is giving full control to the user, and respecting them enough to allow them to make mistakes. If I didn't want that I'd be using a more restrictive OS.
BTW, a good middle ground between raw `rm` and `trash-put` is `alias rm='rm -i'`. This way you can confirm deletions or pass `-f` to force it.
- mekster 5y ago> `alias rm='rm -i'` Done that 15 years ago. Ended up using -f because the confirmation got annoying fast. Landed onto using trash-cli and never had to bother anything when rm'ing. You can add 'trash-empty 30' in daily cron to delete files older than 30 days in the trash.