rgrc(1)

okay bestie, pull up a chair 💅 you're reading rgrc(1) from the General Commands Manual — yes, that one. let's get into it.

🎀 NAME 🎀

rgrc — Rusty Generic Colouriser 🦋

---

✨ SYNOPSIS ✨

rgrc [options] COMMAND [args] ...

🌸 DESCRIPTION 🌸

so what does this icon actually do? rgrc runs any command you throw at it and colourises its output according to a set of rules. that's the whole vibe. the rules get imported from grc and grcat configuration files. slay. ✨

---

👑 OPTIONS 👑

here's the full menu, no cap, nothing skipped:

• --help — shows you a lil summary of the options. classic.
• --aliases — spits out a list of shell commands that generate aliases for the binaries that are supported and installed. 🫶
• --all-aliases — same energy but for all supported binaries, installed or not.
• --except=alias[,alias[,...]] — a list of aliases to leave out of the shell commands that –aliases or –all-aliases generate. it's the "not you" list 🙈
• --color=[on,off,auto] — turn colour output on or off. default is auto. 🎨
• --completions=SHELL — prints a shell completion script for SHELL. supported: bash, zsh, fish, ash.
• --flush-cache — flushes and rebuilds the embedded configuration cache. heads up: only available when built with embed-configs.
• --config, -c NAME — explicit config file name (e.g., df to load conf.df).
• --version, -V — prints the installed rgrc version and dips. ✌️
• --verbose[=LEVEL], -v, -vv — enables rule-level debug output. heads up: only available when the binary is built with the debug feature. if you give it with no value, it behaves like --verbose=1. here are the debug levels, bestie:
  • --verbose[=1] or -v (Basic): shows the matched rules count and the style count for each line.
    • format: [Line N] ✓ Matched M rule(s): #R (S style(s)), ...
  • --verbose=2 or -vv (Verbose): shows the detailed matching info, including:
    • rule regex patterns
    • matched text with capture groups (space-separated)
    • applied styles for each capture group

---

🦋 CONFIGURATION FILES 🦋

rgrc reads its config from all of these locations (same format as rgrc.conf), if they're there. all matching rules get read and used — it's not a pick-one situation, it's a whole group chat. 💬

~/.rgrc
~/.config/rgrc/rgrc.conf
/usr/local/etc/rgrc.conf
/etc/rgrc.conf
~/.grc
~/.config/grc/grc.conf
/usr/local/etc/grc.conf
/etc/grc.conf

any grcat configuration (e.g. conf._xyz_) gets searched for in all of these locations. but here's the twist: only the first found file is read and used. 🧚

~/.config/rgrc
~/.local/share/rgrc
/usr/local/share/rgrc
/usr/share/rgrc
~/.config/grc
~/.local/share/grc
/usr/local/share/grc
/usr/share/grc

want to extend the existing config for a command that's already configured? easy. just add a new rule in ~/.rgrc and have a unique conf._command_. and if you want to replace the existing rules for a known command, create ~/.config/rgrc/conf._command_ and it'll be used instead of the one from /usr/share/grc. periodt. 💅

---

🍓 SEE ALSO 🍓

grc(1), grcat(1) — go give them a read too, they're literally the neighbours.

💜 AUTHOR 💜

Written by Lazy Walker l4zywalk3r@gmail.com — king behaviour fr fr. 👑

---

ngl that's the whole page bestie, go colourise something. 🌈

mwah, kisses from the General Commands Manual — rgrc(1), page and section both, no date on this one, and that's the tea 🎀✨