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

Stop Foot telling TUIs a light theme is dark

omarchyomarchy-4footwayland
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

/usr/share/omarchy/default/themed/foot.ini.tpl starts with [colors-dark] and has no initial-color-theme. The quattro copy is byte-identical. omarchy-theme-set-templates loads every key from omarchy-theme-color --all, including mode, so {{ mode }} renders to dark or light. It globs ~/.config/omarchy/themed/*.tpl before the built-ins and skips an output file that already exists, so a user foot.ini.tpl wins. The quattro rewrite to a single awk pass keeps that order. The five stock themes that resolve to mode light are exactly catppuccin-latte, flexoki-light, lupine, rose-pine and white. No stock theme ships foot.ini, and foot.ini is on INSTALLED_THEME_DENIED for git-installed themes, which matches the record's last paragraph. ~/.config/foot/foot.ini has the include line directly under [main]. The foot.ini(5) source on Codeberg says initial-color-theme is a [main] option defaulting to dark, that [colors-dark] is used unless initial-color-theme=light, and that an included file has its own section scope. The installed foot 1.28.0 man page also documents initial-color-theme. Issue #8905 and PR #8907 are both OPEN, and the issue gives the ?997;1n reply quoted in the symptom. Not exercised: regenerating the theme or querying a live Foot window.

Symptom

On Flexoki Light, Catppuccin Latte, Rose Pine, Lupine or White, the Foot terminal is visibly light, but TUIs that ask the terminal for its colour mode (hunk, and other apps using the CSI ?996n colour-scheme query) draw their dark palette, with pale text on my light background. printf '\033[?996n' in Foot answers ^[[?997;1n (dark).

Cause

/usr/share/omarchy/default/themed/foot.ini.tpl always renders the palette into a [colors-dark] section and never sets initial-color-theme. Per foot.ini(5), [colors-dark] is the dark theme and the default unless initial-color-theme=light is set, so Foot reports dark mode whatever the colours are. The theme already declares its mode (mode = "light" in colors.toml, resolved by omarchy-theme-color), and the template engine exposes it as {{ mode }}, but the template does not use it. Upstream issue #8905 and fix PR #8907 are both still open, and the template on quattro still starts with [colors-dark] as of 2026-10-04.

Fix

Override the built-in template with a user template. omarchy-theme-set-templates processes ~/.config/omarchy/themed/*.tpl before the built-ins, and a user template with the same output name means the built-in one is skipped:


mkdir -p ~/.config/omarchy/themed
{
  echo 'initial-color-theme={{ mode }}'
  echo
  sed '1s/^\[colors-dark\]$/[colors-{{ mode }}]/' /usr/share/omarchy/default/themed/foot.ini.tpl
} > ~/.config/omarchy/themed/foot.ini.tpl
head -3 ~/.config/omarchy/themed/foot.ini.tpl
omarchy theme set "$(cat ~/.local/state/omarchy/current/theme.name)"

The generated file is pulled in by include=~/.local/state/omarchy/current/theme/foot.ini at the top of ~/.config/foot/foot.ini. foot.ini(5) states that an included file has its own section scope, so a line before any section header lands in [main] and the rest of your foot.ini is unaffected.

initial-color-theme applies only when a window starts, so close and reopen Foot windows that were already open. Remove ~/.config/omarchy/themed/foot.ini.tpl once upstream ships the fix, so you pick up later changes to the template. A theme that ships its own foot.ini (only possible for a theme you wrote yourself, not a git-installed one) bypasses templates entirely.

Verify

On a light theme, head -3 ~/.local/state/omarchy/current/theme/foot.ini shows initial-color-theme=light and [colors-light]. In a new Foot window, printf '\033[?996n' answers ^[[?997;2n. On a dark theme the same commands show dark and ?997;1n.

Sources

foot-light-theme-reports-dark-mode