Understand why a font change appears to do nothing in an open terminal
The bug is confirmed verbatim. bin/omarchy-font-set contains omarchy-notification-send -g "You must restart Ghostty to see font change" (with the double space) and the same for Foot, so the message lands in the -g/--glyph value slot and leaves no headline. Two corrections: the cause is wrong that these are 'its last statements'. omarchy-hook font-set "$font_name" runs after them, so the script's exit status comes from the hook, not from the failed notification. More importantly the sudo sed -i patch targets a package-owned file that omarchy update/pacman restores, silently reverting the patch. A font-set hook achieves the same thing durably and without sudo.
omarchy-font-set lives in a package-owned path, so a sed patch to it is reverted on the next omarchy update.
Symptom
You change the font via Style > Font or omarchy font set "JetBrainsMono Nerd Font", the command exits successfully, but the running Ghostty or Foot window keeps the old font and no notification ever appears. It reads as "the font change didn't work". Running the underlying command by hand prints Usage: omarchy-notification-send [--exec <command>] [--app-name <app-name>] [-g <glyph>] ... <headline> [description] [notify-send options].
Cause
Ghostty and Foot only read the font face at process start. omarchy-font-set is supposed to tell you to restart them, but lines 71 and 75 of bin/omarchy-font-set call omarchy-notification-send -g "You must restart Ghostty to see font change". The message lands in the -g/--glyph slot, which takes a value, leaving no headline argument. omarchy-notification-send then prints its usage line and exits 1. The script has no set -e, and omarchy-hook font-set "$font_name" runs after those lines, so the script's exit status comes from the hook rather than the failed notification. The reminder is dropped completely silently.
Fix
The font change did apply. Just restart the terminals. **This closes all their windows, so save your work first:**
pkill -x ghostty
pkill -x foot
Confirm the setting really did change before restarting:
fc-match monospace
grep -i 'font' ~/.config/ghostty/config
grep '^font=' ~/.config/foot/foot.ini
Correction to the cause: the two broken calls are **not** the script's last statements. omarchy-hook font-set "$font_name" runs after them, so the exit status comes from the hook rather than from the failed notification. The -g bug itself is real and verbatim in the source. It just fails silently for a different reason than stated.
Do **not** sudo sed the packaged script. bin/omarchy-font-set is package-owned and omarchy update restores it, silently reverting your patch. Get the notification back with a font-set hook instead, which Omarchy runs at the end of every font change:
mkdir -p ~/.config/omarchy/hooks/font-set.d
cat > ~/.config/omarchy/hooks/font-set.d/30-restart-notice.sh <<'EOF'
#!/bin/bash
pgrep -x ghostty >/dev/null && omarchy-notification-send "Restart Ghostty to see the font change"
pgrep -x foot >/dev/null && omarchy-notification-send "Restart Foot to see the font change"
exit 0
EOF
chmod +x ~/.config/omarchy/hooks/font-set.d/30-restart-notice.sh
Verify
A newly opened Ghostty/Foot window renders in the new font. omarchy-notification-send "test" "test"; echo $? returns 0 and shows a toast, confirming the notification path itself is healthy.