Make Ghostty honor its own font-family instead of the global Omarchy font
Same confirmed root cause as the family-hijack record. The strong prepend_first rule on monospace is verbatim in bin/omarchy-font-set, and Ghostty's ? include prefix is correct optional-include syntax. Diagnostics are all valid. Two gaps. First, the referenced fonts.conf rewrite is undone by the next omarchy font set (the script regenerates the file unconditionally), so the fix needs the font-set hook. Second, pkill -x ghostty closes every Ghostty window including any with unsaved work in running programs, which is stated without warning.
Moving ~/.config/fontconfig/fonts.conf aside also drops the global Style > Font selection for every app that asks for generic monospace.
Symptom
~/.config/ghostty/config sets font-family = JetBrainsMono Nerd Font Mono and ghostty +show-config confirms it, but the terminal visibly renders in the Omarchy system font. ghostty +show-face --string='abc012Il1' resolves to the global font instead, e.g. file: "/usr/share/fonts/TTF/CaskaydiaCoveNerdFontMono-Regular.ttf".
Cause
Same root as the family-hijack bug: omarchy font set writes a strong prepend_first assignment for monospace into ~/.config/fontconfig/fonts.conf. Because 48-guessfamily.conf appends the generic monospace to any family name containing mono, Ghostty's explicit JetBrainsMono Nerd Font Mono request arrives carrying monospace, matches the rule, and the global font is prepended ahead of it with a strong binding. The result is that the global Style > Font selection behaves as an override rather than a default.
Fix
Diagnose:
ghostty +show-config | grep font-family
ghostty +show-face --string='abc012Il1'
fc-match "JetBrainsMono Nerd Font Mono"
Quick proof that fontconfig, not Ghostty, is the culprit:
mv ~/.config/fontconfig/fonts.conf{,.off}
ghostty +show-face --string='abc012Il1' # now resolves to JetBrainsMono
mv ~/.config/fontconfig/fonts.conf{.off,}
Apply the alias/prefer rewrite **via a font-set hook**, not by hand. omarchy-font-set rewrites ~/.config/fontconfig/fonts.conf from scratch on every font change, so a hand-edit survives only until the next Style > Font pick:
mkdir -p ~/.config/omarchy/hooks/font-set.d
cat > ~/.config/omarchy/hooks/font-set.d/20-font-alias.sh <<'EOF'
#!/bin/bash
font="$1"
[[ -n $font ]] || exit 0
mkdir -p ~/.config/fontconfig
cat > ~/.config/fontconfig/fonts.conf <<XML
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd">
<fontconfig>
<alias binding="strong">
<family>monospace</family>
<prefer><family>$font</family></prefer>
</alias>
</fontconfig>
XML
fc-cache -f
EOF
chmod +x ~/.config/omarchy/hooks/font-set.d/20-font-alias.sh
fc-cache -f
Then fully restart Ghostty. It reads its face only at startup. **This closes every Ghostty window, so save your work first** (pkill -SIGUSR2 ghostty reloads config but will not re-resolve the font face):
pkill -x ghostty
If fc-match monospace still returns JetBrainsMono, /etc/fonts/conf.d/50-omarchy.conf's mode="assign" generic rule is still winning. See the omarchy-font-set-hijacks-named-mono-families fix for the user-tree override that sorts after it.
Verify
ghostty +show-face --string='abc012Il1' reports the file path of the font named in ~/.config/ghostty/config, while fc-match monospace still returns the Omarchy global font.