rFortune

rFortune is a modern, cross-platform reimplementation of the classic Unix fortune program, written in Rust.

It displays a random quote or witty phrase from a plain text file, making it perfect for terminal startup messages, scripting, or just a bit of inspiration.

✨ New in v0.5.5

📚 Multiple fortune file support

• Added support for multiple fortune files via the repeatable option --file <PATH>.
  Example:

  rfortune --file ~/fortunes/dev --file ~/fortunes/humor
  

• Introduced the new configuration key fortune_files (list). When defined, it takes priority over default_file.
• Automatic config migration: if fortune_files is missing or empty, it is initialized automatically with the previous default_file value.
• Unified JSON-based cache shared across all configured fortune files.
• Intelligent no-repeat mechanism: rFortune now avoids showing the same quote twice in a row from the same file.

🔒 Cache robustness improvements

• Cache writes to the shared JSON store are now atomic: data is written to a temporary file and then replaced via rename to avoid partial/corrupted writes.
• Advisory file locking (via the fs2 crate) is used to protect concurrent access to the shared cache ( last_quotes.json). This reduces races when multiple rFortune processes run simultaneously.
• Windows fallback: on platforms with older rename semantics the implementation attempts a remove+rename fallback to ensure the store is replaced reliably.
• Internal cleanup: introduced a small open_and_lock() helper to centralize file opening/locking logic and switched internal cache APIs to use anyhow for richer error context.
• Added an integration test (tests/cache_tests.rs) and the dependencies fs2 and anyhow.

🧭 Improved cross-platform behavior

• Fixed an issue with the app_dir() function on Linux and macOS where dirs::data_dir() could return None in CI or headless environments.
• Added reliable fallbacks ensuring consistent paths:
  • macOS → $HOME/Library/Application Support/rfortune
  • Linux → $HOME/.local/share/rfortune
• Fixed inconsistent cache path resolution caused by incorrect app_dir() usage on Linux/macOS.
• Introduced the new helper function ensure_cache_dir() to centralize cache directory creation, improving reliability across save_last_cache() and save_last_cache_json().
• Ensures predictable configuration and cache directory behavior across all systems, including GitHub Actions.

⚙️ Deprecated

• The old files_fortune key and single-file print_random() function have been removed or replaced by the new multi-file logic.

🚀 Features

• ✅ Cross-platform: works on Linux, Windows, macOS Intel and Apple Silicon
• ⚡ Fast and lightweight (native Rust binary)
• 📁 Simple input format: one or more lines per fortune, separated by %
• 🌹 UTF-8 support for multilingual content
• 🧩 Easily extensible
• 🧠 Built-in cache system to avoid showing the same fortune twice in a row
• ✨ New CLI with subcommands for config, file initialization and cache management

📦 Installation

🐧 AUR (Arch Linux)

yay -S rfortune
# or
paru -S rfortune

🍺 Homebrew (macOS/Linux)

brew tap umpire274/tap
brew install rfortune

🦀 Crates.io (Rust)

cargo install rfortune

📥 Download

Precompiled binaries are available in the Releases section.

🔐 GPG Signature

All release archives are cryptographically signed with GPG.

• .sig files contain the ASCII-armored detached signature for the corresponding archive.
• You can verify the archive with:

gpg --verify rfortune-<version>-<target>.tar.gz.sig rfortune-<version>-<target>.tar.gz

🔑 Public Key

The releases are signed with the following GPG key:

• Key ID: 423FABCE0A1921FB
• Fingerprint: 8118 9716 9512 2A32 1F3D C04C 423F ABCE 0A19 21FB
• Download: https://github.com/umpire274.gpg

To import the key from a keyserver:

gpg --recv-keys 423FABCE0A1921FB

Or from OpenPGP server:

gpg --keyserver keys.openpgp.org --recv-keys 423FABCE0A1921FB

Then verify the fingerprint:

gpg --fingerprint 423FABCE0A1921FB

🚀 Usage

rfortune [OPTIONS]
rfortune <SUBCOMMAND>

Running rfortune without subcommands prints a random fortune from the default file (rfortune.dat).

⚙️ First-time setup

When rfortune is launched for the first time and no configuration directory exists,
the application will ask whether to initialize its environment (creating the default
configuration and fortune files).
In non-interactive contexts, initialization happens automatically.

🧩 Options & Subcommands

💡 Examples

# Print a random fortune from the default file (rfortune.dat)
rfortune

# Print a random fortune from a specific file
rfortune --file ~/fortunes/misc

# Create the default configuration file in the user data directory
rfortune config init

# Open the configuration file in the system’s default text editor
rfortune config edit

# Open the configuration file with a specific editor (e.g. vi, nano, code)
rfortune config edit --editor vi

# Create a sample default fortune file (rfortune.dat)
rfortune file init

# Clear all cached last-used fortunes
rfortune cache clear

Configuration (rfortune.conf)

Example:

default_file: "/home/user/.local/share/rfortune/rfortune.dat"
print_title: true
use_cache: true

# Optional: load additional quote files
fortune_files:
  - "/usr/local/share/rfortune/philosophy.fort"
  - "/usr/local/share/rfortune/tech.fort"

Priority order:

1. --file <PATH> CLI argument(s)
2. fortune_files list in config
3. default_file

Multiple Sources Configuration

You can load quotes from multiple files and rfortune will automatically choose one at random:

rfortune --file my_quotes.fort --file jokes.fort --file tech.fort

Or configure them permanently:

fortune_files:
  - "/path/to/my_quotes.fort"
  - "/path/to/jokes.fort"

If both are present, CLI always wins.

Smart Quote Repetition Avoidance

rfortune keeps a small cache and automatically avoids repeating the same quote twice in a row, but only for quotes from the same file.

This keeps the output natural across multiple sources.

Migration from older versions

If your previous configuration did not contain fortune_files, rfortune will automatically migrate your config by adding it and setting:

fortune_files:
  - default_file

No manual action is required.

📁 Fortune File Format

Each fortune must be on one or more lines separated by %, like so:

%
The best way to get a good idea is to get a lot of ideas.
%
Do or do not. There is no try.
%
To iterate is human, to recurse divine.
%

You may optionally add a title at the top of the file by starting the first line with #. The title will be printed before the random quote:

# Murphy's Laws
%
Anything that can go wrong will go wrong.
%
If there's a possibility of several things going wrong, the one that will cause the most damage will be the one to go wrong.
%

🔒 License

This project is licensed under the MIT License.

© 2025 Alessandro Maestri

💡 Contributing

Pull requests are welcome! If you’d like to add support for more languages, improve performance, or fix bugs, feel free to fork the repo and contribute.

🙌 Acknowledgments

Inspired by the classic BSD fortune program. Built with ❤️ in Rust.