OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-theming medium common DISPUTE

Fix "failed to parse rgb color {{ color8 }}" after creating a theme with Aether

omarchyomarchy-4hyprlandwayland
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The mechanism is real, because omarchy-theme-set-templates substitutes {{ key }} by building a sed script only from keys present in the theme, so any placeholder with no matching key survives verbatim into the generated config and the consuming app tries to parse it. But the prescribed fix is aimed at an outdated schema. docs/theming.md shows current colors.toml is semantic-first (accent, selection, muted, the background/foreground ramps, named colours), and explicitly states that muted 'also serves as ANSI color8' and that accent falls back to color4. Legacy colorN names are still supported and resolved canonical values are re-exposed through them. So dumping a bare color0..color15 list can leave templates referencing {{ muted }}, {{ accent }} or {{ bright_foreground }} still unsubstituted. The verification grep and the copy-a-stock-theme advice are both correct and worth keeping.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

After building a custom theme in Aether, some apps break: the Wi-Fi panel and similar surfaces fail with an error like failed to parse rgb color {{ color8 }}. Alacritty is most affected. Stock themes work fine.

Cause

Omarchy renders per-app configs from templates in default/themed/*.tpl by pure sed substitution of {{ key }} placeholders out of the theme's colors.toml. Aether writes a colors.toml that does not define the full color0..color15 ANSI palette, so any placeholder with no matching key is left in the output verbatim and the consuming app tries to parse the literal string {{ color8 }} as a color.

Fix

The mechanism is real: omarchy-theme-set-templates substitutes {{ key }} via a sed script built only from keys your theme actually defines, so any placeholder with no matching key survives verbatim into the generated config.

But current Omarchy's colors.toml is **semantic-first**, not a raw ANSI list, so supply the canonical keys:


nvim ~/.config/omarchy/themes/<my-theme>/colors.toml

mode = "dark"

accent    = "#7aa2f7"
selection = "#292e42"
muted     = "#414868"     # also serves as ANSI color8

background         = "#1a1b26"
dark_background    = "#13141c"
darker_background  = "#0e0e14"
lighter_background = "#24283b"

foreground        = "#a9b1d6"
dark_foreground   = "#565f89"
light_foreground  = "#b4bee6"
bright_foreground = "#c0caf5"

red  = "#f7768e"
blue = "#7aa2f7"

Per docs/theming.md: muted also serves as ANSI color8, accent falls back to color4 when absent, and red/color1 populates the shell's urgent role. Legacy colorN names still work and adding color0..color15 does no harm, but they alone will not satisfy templates that reference {{ muted }}, {{ accent }} or {{ bright_foreground }}, which is why the bare 16-colour list is not sufficient.

Re-apply and verify nothing was left unsubstituted:


omarchy theme set <my-theme>
grep -rn '{{' ~/.local/state/omarchy/current/theme/ || echo "all placeholders resolved"

The reliable way to start a theme is still to copy a stock one, which already has every key:


cp -a ~/.local/share/omarchy/themes/tokyo-night ~/.config/omarchy/themes/my-theme

Verify

grep -rn '{{' ~/.local/state/omarchy/current/theme/ returns nothing, and the Wi-Fi panel and Alacritty open without the rgb parse error.

Sources

custom-theme-missing-color-keys-rgb-parse-error