mirror of
https://github.com/nivekuil/rip
synced 2025-02-17 04:28:26 +00:00
Update info about changing graveyard directory
This commit is contained in:
parent
c297dc06af
commit
d601ffd137
1 changed files with 6 additions and 3 deletions
|
@ -1,12 +1,15 @@
|
|||
* rip (Rm ImProved)
|
||||
Deleted files get sent to the graveyard (=/tmp/.graveyard= by default) under their absolute path) instead of being unlinked, giving you a chance to recover them.
|
||||
Deleted files get sent to the graveyard (=/tmp/.graveyard= by default, under their absolute path) instead of being unlinked, giving you a chance to recover them.
|
||||
|
||||
No data is overwritten. If files that share the same path are deleted, they will be renamed as numbered backups.
|
||||
|
||||
If you want to put the graveyard somewhere else (like =~/.local/share/Trash=), you could alias =rip= to =rip --graveyard ~/.local/share/Trash=. This can be a good idea because if the graveyard is in a tmpfs mount, deleting large files can quickly fill up your RAM. It's also slower than moving files within the same filesystem.
|
||||
If you want to put the graveyard somewhere else (like =~/.local/share/Trash=), you have two options, in order of precedence:
|
||||
1. Alias =rip= to =rip --graveyard ~/.local/share/Trash=
|
||||
2. Set the environment variable =$GRAVEYARD= to =~/.local/share/Trash=
|
||||
This can be a good idea because if the graveyard is in a tmpfs mount, deleting large files can quickly fill up your RAM. It's also much slower to move files across filesystems, although the delay should be unnoticable with an SSD.
|
||||
|
||||
** Installation
|
||||
Get a binary [[https://github.com/nivekuil/rip/releases][release]] (x86_64) or =cargo install rm-improved=.
|
||||
Get a binary [[https://github.com/nivekuil/rip/releases][release]] (x86_64) or build it with =cargo install rm-improved=.
|
||||
|
||||
** Usage
|
||||
#+BEGIN_EXAMPLE
|
||||
|
|
Loading…
Add table
Reference in a new issue