#trash #rm #safe

app rm-improved

rip: a safe and ergonomic alternative to rm

27 releases

0.13.1 Feb 28, 2020
0.12.0 Dec 24, 2018
0.11.4 Jan 31, 2017
0.11.2 Dec 22, 2016
0.11.1 Nov 8, 2016

#2326 in Command line utilities

Download history 129/week @ 2023-02-12 57/week @ 2023-02-19 95/week @ 2023-02-26 57/week @ 2023-03-05 51/week @ 2023-03-12 34/week @ 2023-03-19 50/week @ 2023-03-26 93/week @ 2023-04-02 64/week @ 2023-04-09 80/week @ 2023-04-16 39/week @ 2023-04-23 41/week @ 2023-04-30 83/week @ 2023-05-07 31/week @ 2023-05-14 37/week @ 2023-05-21 70/week @ 2023-05-28

230 downloads per month


472 lines

* rip (Rm ImProved)

=rip= is a command-line deletion tool focused on safety, ergonomics, and performance. It favors a simple interface, and does /not/ implement the xdg-trash spec or attempt to achieve the same goals.

Deleted files get sent to the graveyard (=/tmp/graveyard-$USER= by default, see [[https://github.com/nivekuil/rip#-notes][notes]] on changing this) under their absolute path, 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.

=rip= is made for lazy people. If any part of the interface could be more intuitive, please open an issue or pull request.

** ⚰ Installation
Or get a binary [[https://github.com/nivekuil/rip/releases][release]] (Linux x86_64, ARMv7 and macOS), untar it, and move it somewhere on your $PATH:
$ tar xvzf rip-*.tar.gz
$ mv rip /usr/local/bin

or build it:
$ cargo install rm-improved

Arch Linux users can install it from the [[https://aur.archlinux.org/packages/rm-improved/][AUR]] (thanks @Charon77!)
$ yay -S rm-improved
** ⚰ Usage

-d, --decompose Permanently deletes (unlink) the entire graveyard
-h, --help Prints help information
-i, --inspect Prints some info about TARGET before prompting for action
-s, --seance Prints files that were sent under the current directory
-V, --version Prints version information

--graveyard <graveyard> Directory where deleted files go to rest
-u, --unbury <target> Undo the last removal by the current user, or specify some file(s) in the graveyard. Combine with -s to restore everything printed by -s.

<TARGET>... File or directory to remove
Basic usage -- easier than rm
$ rip dir1/ file1
Undo the last deletion
$ rip -u
Returned /tmp/graveyard-jack/home/jack/file1 to /home/jack/file1
Print some info (size and first few lines in a file, total size and first few files in a directory) about the target and then prompt for deletion
$ rip -i file1
dir1: file, 1337 bytes including:
> Position: Shooting Guard and Small Forward ▪ Shoots: Right
> 6-6, 185lb (198cm, 83kg)
Send file1 to the graveyard? (y/n) y
Print files that were deleted from under the current directory
$ rip -s
Name conflicts are resolved
$ touch file1
$ rip file1
$ rip -s
-u also takes the path of a file in the graveyard
$ rip -u /tmp/graveyard-jack/home/jack/file1
Returned /tmp/graveyard-jack/home/jack/file1 to /home/jack/file1
Combine -u and -s to restore everything printed by -s
$ rip -su
Returned /tmp/graveyard-jack/home/jack/dir1 to /home/jack/dir1
Returned /tmp/graveyard-jack/home/jack/file1~1 to /home/jack/file1~1
** ⚰ Notes
- You probably shouldn't alias =rm= to =rip=. Unlearning muscle memory is hard, but it's harder to ensure that every =rm= you make (as different users, from different machines and application environments) is the aliased one.
- If you have =$XDG_DATA_HOME= environment variable set, =rip= will use =$XDG_DATA_HOME/graveyard= instead of the =/tmp/graveyard-$USER=.
- 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 mounted on an in-memory filesystem (as /tmp is in Arch Linux), deleting large files can quickly fill up your RAM. It's also much slower to move files across filesystems, although the delay should be minimal with an SSD.
- In general, a deletion followed by a =--unbury= should be idempotent.
- The deletion log is kept in =.record=, found in the top level of the graveyard.


~100K SLoC