Fix a `shell.lock.toml` section override that is silently ignored
Checked line by line against /usr/share/omarchy/bin/omarchy-theme-set-templates on this workstation at omarchy 4.0.2-1, and against upstream docs/theming.md on omacom/omarchy at quattro, which I fetched in full. Every mechanical claim holds at the line numbers the record gives. apply_shell_section_override begins at line 313 with [[ -f $NEXT_THEME_DIR/shell.toml ]] || return. The section name comes from the filename via section=${section#shell.} and section=${section%.toml} at lines 317 and 318, so a misspelt shell.lockscreen.toml is spliced in as a [lockscreen] section nothing reads. strip_shell_section_header removes a matching header so the header inside the file is optional. The whole template pass including shell.toml sits inside if [[ -f $COLORS_FILE ]] at line 371, and apply_shell_section_overrides runs at line 404 outside that gate but returns immediately because no shell.toml was generated. Line 396 if [[ ! -f $output_path ]] confirms a hand-written shell.toml in the theme wins over the template outright. Upstream documents the same thing in its own words: shell.lock.toml replaces only the [lock] section after the default shell.toml has been generated, the filename decides the target section so the [lock] header is optional, and a theme's own shell.toml wins over default/themed/shell.toml.tpl. The file name is real and shipped: /usr/share/omarchy/themes/tokyo-night/shell.lock.toml exists and is the only one of its kind across the 22 theme directories, and it carries bare keys with no header, exactly as the record advises. The section list in the fix matches the generated file on this machine exactly: grep -o '^\[[a-z-]*\]' ~/.local/state/omarchy/current/theme/shell.toml returns bar, hyprland, controls, spacing, font, popups, tooltip, notifications, launcher, menu, polkit, lock, image-picker, and default/themed/shell.toml.tpl has the same 13 headers. Every [lock] key in the example is a real token in that template's [lock] block, and selection and selection-alpha also exist without being required. The user layer is real and works the way the record says: shell/Commons/Color.qml declares a watched FileView at root.home + "/.config/omarchy/shell.toml" and mergeShell() merges theme values first then user values, with the comment that user keys win so a machine-level ~/.config/omarchy/shell.toml survives theme switches. That file exists here with [font] base-size = 12 in it, and it is distinct from ~/.config/omarchy/shell.json, which is behaviour and bar layout rather than colour, so the record points a user at the right one. omarchy restart shell and omarchy system lock both route to real scripts, omarchy-restart-shell and omarchy-system-lock, confirmed from their omarchy:examples metadata. Copying /usr/share/omarchy/themes/tokyo-night/colors.toml works for a cloned theme too, because colors.toml is not on INSTALLED_THEME_DENIED in omarchy-theme-set. Two nuances that do not make the record wrong. The symptom says the lock surface keeps the generated colours. When shell.toml is missing entirely, Color.qml's onLoadFailed calls loadShell("") and the surface falls back to the foundational palette from colors.toml, or to the QML defaults if that is missing too, so nothing changes either way but the wording is loose. And as the record's own audit note already says, a wrong header inside the override file is not literally ignored, it survives into the spliced body, and the record's practical advice to write only the keys avoids that. Severity low and frequency occasional are right: nothing breaks, a restyle is silently skipped. I did NOT exercise any of this. I did not run omarchy-theme-set, did not add a shell.*.toml to any theme, and did not lock the session, so the splicing behaviour is read from the awk in apply_shell_section_override and from upstream's documentation rather than from a run. I only updated the sources: the repo has been renamed from basecamp/omarchy to omacom/omarchy, so the three cited blob URLs are replaced with the current name, and I retrieved docs/theming.md at quattro to confirm it says what the record needs.
Shipping a complete hand-written shell.toml in a theme replaces the generated file entirely. omarchy-theme-set-templates will not overwrite it, so any key later Omarchy releases add is missing and those surfaces silently fall back to built-in defaults. Prefer a shell.<section>.toml, or ~/.config/omarchy/shell.toml, both of which layer rather than replace.
Symptom
You add shell.lock.toml to your theme to restyle the lock screen (or shell.menu.toml, shell.notifications.toml, …) and nothing changes. The lock surface keeps the generated colours, with no warning anywhere. ls ~/.local/state/omarchy/current/theme/shell.toml reports No such file or directory, and grep -A5 '^\[lock\]' ~/.local/state/omarchy/current/theme/shell.toml fails because there is no file to grep.
Cause
A shell.<section>.toml is not a standalone file. apply_shell_section_override in bin/omarchy-theme-set-templates splices its body into the generated shell.toml, and its very first line is [[ -f $NEXT_THEME_DIR/shell.toml ]] || return. shell.toml itself is only rendered from default/themed/shell.toml.tpl inside the if [[ -f $COLORS_FILE ]] gate, so a partial theme with no colors.toml produces no shell.toml and every section override is dropped without a message. Two smaller traps sit on top of that: the **filename** decides the target section (so the [lock] header inside the file is optional and a wrong header is ignored), and a misspelt filename such as shell.lockscreen.toml is happily appended as a [lockscreen] section that the shell never reads, again silently. Note also that a theme shipping a full hand-written shell.toml wins over the template outright, because omarchy-theme-set-templates never overwrites an output file that already exists.
Fix
Confirm the generated file exists at all. This is almost always the whole problem:
ls -l ~/.local/state/omarchy/current/theme/colors.toml ~/.local/state/omarchy/current/theme/shell.toml
If colors.toml is missing, give the theme one. That is what makes the entire template pass run:
cp /usr/share/omarchy/themes/tokyo-night/colors.toml ~/.config/omarchy/themes/<name>/colors.toml
omarchy theme set <name>
Get the section name right: the valid ones are exactly the sections in the generated file:
grep -o '^\[[a-z-]*\]' ~/.local/state/omarchy/current/theme/shell.toml
# [bar] [hyprland] [controls] [popups] [tooltip] [notifications] [launcher]
# [menu] [polkit] [lock] [image-picker] [spacing] [font]
Write the override with just the keys: the header is optional because the filename decides the section:
cat > ~/.config/omarchy/themes/<name>/shell.lock.toml <<'EOF'
background = "#000000"
background-alpha = 0.8
text = "#ffffff"
placeholder = "#ffffff"
text-error = "#ff5555"
border = "#ffffff"
border-active = "#ffffff"
border-error = "#ff5555"
border-alpha = 1.0
EOF
omarchy theme set <name>
Then check that it actually landed in the generated file:
sed -n '/^\[lock\]/,/^\[/p' ~/.local/state/omarchy/current/theme/shell.toml
If you want the override on **every** theme rather than one, put it in your own file instead: ~/.config/omarchy/shell.toml layers over whatever the theme generated and survives theme switches:
[lock]
border = "#ffffff"
omarchy restart shell # the shell watches the file; usually not needed
omarchy system lock # check it
Verify
sed -n '/^\[lock\]/,/^\[/p' ~/.local/state/omarchy/current/theme/shell.toml shows your values, and omarchy system lock displays the restyled password input.