rip2 0.2.0

rip: a safe and ergonomic alternative to rm
Documentation

rip 2

Test Coverage Status

rip is a rust-based rm with a focus 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 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.

This version is a fork-of-a-fork:

  1. nivekuil/rip, the original, which has been unmaintained since 2020.
  2. StandingPadAnimation/rip who added a few features.
  3. Finally, that repo was forked @here with ongoing maintenance:
    • Added shell completions
    • Added a test suite
    • Added a few unmerged PRs from the original repo
    • General maintenance:
      • Bug fix for FIFO file copy not being executed
      • Refactoring to modern rust

Installation

You can install this package from source with:

$ cargo install rip2

No binaries are made available at this time.

Usage

Usage: rip [OPTIONS] [TARGETS]...

Arguments:
  [TARGETS]...  File or directory to remove or unbury

Flags:
  -u, --unbury                 Restore the specified files or the last file if none are specified
  -s, --seance                 Prints files that were deleted in the current working directory
  -i, --inspect                Print some info about TARGET before burying
  -d, --decompose              Permanently deletes the graveyard
  -h, --help                   Print help
  -V, --version                Print version

Options:
      --graveyard <GRAVEYARD>  Directory where deleted files rest
      --completions <SHELL>    Generate shell completions file for the specified shell

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
/tmp/graveyard-jack/home/jack/file1
/tmp/graveyard-jack/home/jack/dir1

Name conflicts are resolved

$ touch file1
$ rip file1
$ rip -s
/tmp/graveyard-jack/home/jack/dir1
/tmp/graveyard-jack/home/jack/file1
/tmp/graveyard-jack/home/jack/file1~1

-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

Aliases.

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.

What I instead recommend is aliasing rm to an echo statement that simply reminds you to use rip:

alias rm="echo Use 'rip' instead of rm."

Graveyard location.

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 $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.

Miscellaneous.

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.