3 ms·
Author acknowledges how the tmpdir can be a bad default, so that’s why you can change it :) > Graveyard location. > You can see the current graveyard location
by xyst 2y ago
Author acknowledges how the tmpdir can be a bad default, so that’s why you can change it :)
> Graveyard location.
> You can see the current graveyard location by running rip graveyard. If you have $XDG_DATA_HOME environment variable set, rip will use $XDG_DATA_HOME/graveyard instead of the $TMPDIR/graveyard-$USER.
> If you want to put the graveyard somewhere else (like ~/.local/share/Trash), you have two options, in order of precedence:
> Alias rip to rip --graveyard ~/.local/share/Trash
> Set the environment variable $RIP_GRAVEYARD to ~/.local/share/Trash.
> This can be a good idea because if the graveyard is mounted on an in-memory file system (as /tmp is in Arch Linux), deleting large files can quickly fill up your RAM. It's also much slower to move files across file systems, although the delay should be minimal with an SSD.
- beanjuiceII 2y ago>rip is a rust-based rm with a focus on safety, ergonomics, and performance then puts the default trash location in /tmp ? knowing its a bad decision? kinda makes me leery of the rest with this kind of reasoning skills
- stavros 2y agoYeah, I can't disagree with this, knowing that something is a bad default and still using it isn't fantastic. It would be much better to put the files somewhere else and clear old files whenever rip was run.
- forgotpwd16 2y ago>~/.local/share/Trash Kinda bad example since this tool doesn't follow xdg-trash spec per README. Tools that do (such as the file managers from the big DEs) use this directory.