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

Fix window border colors and rounding that never change with a community theme

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

Re-audited on this workstation at omarchy 4.0.2-1, omarchy-settings 4.0.2-1, Hyprland 0.56.2-1, and against bin/omarchy-theme-set and default/themed/hyprland.lua.tpl on the quattro branch. The premise holds and is Lua, not hyprlang: 5 of the 22 themes in /usr/share/omarchy/themes (kanagawa, last-horizon, lumon, retro-82, solitude) ship a real hyprland.lua using hl.config({ general = { col = { active_border = ... } } }), default/hypr/omarchy.lua ends with require_optional.module("omarchy.current.theme.hyprland"), and default/hypr/envs.lua requires omarchy.current.theme.gum_env. The mechanism in the cause is correct line for line on the installed script: INSTALLED_THEME_DENIED=(alacritty.toml foot.ini ghostty.conf kitty.conf vscode.json), is_denied_installed_file returns 0 for every *.lua, theme_came_from_a_repo is [[ ! -L $source && -d $source/.git ]], report_ignored_theme_files emits the two quoted stderr lines byte for byte, and omarchy-restart-hyprctl is literally hyprctl reload and sits in post_theme_commands. The fix is correct and its paths are Omarchy 4, not Omarchy 3: ~/.config/hypr/looknfeel.lua exists and ships as an all-comment file, config/hypr/hyprland.lua requires hypr.looknfeel after default.hypr.omarchy, omarchy theme refresh is a real subcommand that re-runs omarchy-theme-set with OMARCHY_THEME_SKIP_BACKGROUND=1, omarchy-theme-color accepts an arbitrary hyprland_active_border key whose value charset covers rgba(33ccffee) rgba(00ff99ee) 45deg, and docs/theming.md on quattro documents that exact TOML line and the hypr_gradient helper. The danger is right too: omarchy-theme-extras selects on -d $theme/.git, so removing .git really does drop the theme out of omarchy theme update. What was wrong is the symptom, and it is wrong in the common case rather than an edge case. The template resolves hyprland_active_border with accent as its fallback, so any cloned theme with a colors.toml does repaint the border. Confirmed live on this machine: the current theme is gruvbox, the staged /home/techluddite/.local/state/omarchy/current/theme/hyprland.lua reads local active_border_color = "#7daea3" which is gruvbox's accent, and hyprctl getoption general:col.active_border returns gradient data: ff7daea3 0deg, not the stock rgba(33ccffee) rgba(00ff99ee) 45deg the record quotes. The record also quotes hyprctl as printing rgba() notation, which it does not. Symptom and verify are rewritten for both points. Issue 8393 was read in full and supports the claim exactly, including that the menu discards stderr and that rounding, shadow and blur go missing. Issue 7884 is the merged change that introduced the policy and supports the cause. Not exercised: no theme was installed, set, removed or refreshed on this machine, and no cloned theme was staged, so the stderr lines and the rm -rf .git promotion path were read from the script rather than triggered.

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

Deleting .git from a theme directory promotes the whole tree to a hand-written theme, so Omarchy stages **every** file the stranger's repo shipped, including hyprland.lua and gum_env.lua, which Hyprland executes at login, and neovim.lua, which Neovim executes at startup. A bad or hostile file there can leave you with a session that will not start. Read them before you do this, and note that it also breaks omarchy theme update for that theme, since there is no longer a repo to pull from.

Symptom

You install a theme with omarchy theme install <git-url> and the bar, terminal and shell all retint, but the theme's own Hyprland look never arrives. Its rounding, shadow and blur are missing entirely, and the window border comes out as a flat version of the theme's accent colour instead of the gradient or the exact colour the author wrote. In the rarer case where the cloned theme ships no colors.toml and no alacritty.toml to derive one from, the borders instead stay on Omarchy's stock cyan-to-green gradient for every theme you switch to. Running the switch from a terminal instead of the menu prints Ignored in /home/<user>/.config/omarchy/themes/<name>: hyprland.lua and A theme installed from a git repo cannot supply Lua, a terminal config, or vscode.json. on stderr. From the Style > Theme menu you see nothing at all. hyprctl getoption general:col.active_border reports a single-stop gradient such as gradient data: ff7daea3 0deg, which is the accent rather than the border the theme author asked for.

Cause

bin/omarchy-theme-set treats any theme directory that contains a .git directory as "came from a stranger" (theme_came_from_a_repo) and refuses to stage anything that can run code. is_denied_installed_file drops every *.lua unconditionally, plus alacritty.toml, foot.ini, ghostty.conf, kitty.conf and vscode.json (INSTALLED_THEME_DENIED). Hyprland requires a theme's hyprland.lua and gum_env.lua at login, so that is deliberate policy, not a bug. What gets staged instead is generated from default/themed/hyprland.lua.tpl, which carries only general.col.active_border / inactive_border and the matching group.col keys, resolved from hyprland_active_border / hyprland_inactive_border in colors.toml with accent and rgba(595959aa) as fallbacks. Rounding, shadow and blur have no colors.toml channel at all, so a theme that expressed its identity in hyprland.lua half-works. The refusal is announced only on stderr, which the menu discards (issue #8393). Separately, even a correct hyprland.lua does not repaint until omarchy-restart-hyprctl (hyprctl reload) has run. It is one of the post_theme_commands, so a theme change that died partway leaves stale borders.

Fix

Confirm this is the refusal and not a broken theme. Run the switch from a terminal so stderr survives:


omarchy-theme-set <name> 2>&1 | sed -n '/^Ignored in/,$p'
[[ -d ~/.config/omarchy/themes/<name>/.git ]] && echo "cloned theme: .lua is dropped by policy"
ls ~/.local/state/omarchy/current/theme/hyprland.lua
grep -n active_border_color ~/.local/state/omarchy/current/theme/hyprland.lua

If the borders are simply stale, reload the compositor:


omarchy-restart-hyprctl        # this is just: hyprctl reload
hyprctl getoption general:col.active_border

**The supported fix** is to express the borders through colors.toml, which a cloned theme *is* allowed to ship. Both a solid colour and a Hyprland gradient work in the same key:


nvim ~/.config/omarchy/themes/<name>/colors.toml

hyprland_active_border   = "rgba(33ccffee) rgba(00ff99ee) 45deg"
hyprland_inactive_border = "rgba(595959aa)"

omarchy theme refresh

Rounding, shadow and blur have no theme channel. Put them in your own Hyprland config, which no theme ever overwrites:


cat >> ~/.config/hypr/looknfeel.lua <<'EOF'

hl.config({
  decoration = {
    rounding = 8,
    shadow = { enabled = true },
    blur = { enabled = true },
  },
})
EOF
hyprctl reload

To run the author's hyprland.lua as written, you must adopt the theme as your own by removing its git checkout. Read the file first (see the risk note):


less ~/.config/omarchy/themes/<name>/hyprland.lua
less ~/.config/omarchy/themes/<name>/neovim.lua
rm -rf ~/.config/omarchy/themes/<name>/.git
omarchy theme set <name>

Verify

grep active_border_color ~/.local/state/omarchy/current/theme/hyprland.lua names the colour you put in colors.toml rather than the theme's bare accent or Omarchy's stock rgba(33ccffee). hyprctl getoption general:col.active_border prints the stops as gradient data: <aarrggbb> [<aarrggbb> ...] <n>deg followed by set: true, so an accent of #7daea3 reads back as gradient data: ff7daea3 0deg and a two-stop gradient reads back as two colour words and a non-zero angle. Switching between two themes visibly changes the focused window's border.

Sources

installed-theme-hyprland-lua-stripped-borders