Get back fontconfig rules that `omarchy font set` wiped from fonts.conf
Read /usr/share/omarchy/bin/omarchy-font-set on 4.0.4-1: line 59 is cat >"$fontconfig_file" <<XML with fontconfig_file=$HOME/.config/fontconfig/fonts.conf, no read and no backup. /etc/snapper/configs holds only root, so /home has no snapshot. /etc/fonts/conf.d/50-user.conf includes fontconfig/conf.d first and fontconfig/fonts.conf second, and 50-omarchy.conf (omarchy-settings 4.0.4-1) sorts before 50-user.conf, so the stated load order is right. fc-conflist exists at /usr/bin/fc-conflist. Issue #12927 (open) states the same truncation, the same lack of backup and the same conf.d drop-in direction. Fix and verify are sound.
Symptom
I had my own rules in ~/.config/fontconfig/fonts.conf (subpixel rgba, a family alias, a substitution for one app). After picking a font in Style > Font, or running omarchy font set, they are all gone. The file now holds only a single monospace block naming my terminal font. No .bak file exists. It happens even when I re-select the font I already had.
Cause
/usr/share/omarchy/bin/omarchy-font-set writes ~/.config/fontconfig/fonts.conf with cat >"$fontconfig_file" <<XML (line 59 on 4.0.4-1). That truncates the file and never reads it first. Unlike omarchy-refresh-config it leaves no timestamped backup. fonts.conf is the user's top-level fontconfig file, so anything else kept there is destroyed on every font change. Fontconfig also reads ~/.config/fontconfig/conf.d/ through /etc/fonts/conf.d/50-user.conf, and the script never touches that directory.
Fix
There is no copy to restore from. Omarchy's snapper config covers root only, so /home has no snapshot. Rewrite your rules from memory or from a dotfiles repo. Put them in a drop-in, never in fonts.conf:
mkdir -p ~/.config/fontconfig/conf.d
cat > ~/.config/fontconfig/conf.d/60-my-rules.conf <<'EOF'
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd">
<fontconfig>
<!-- example: your own rendering rule -->
<match target="font">
<edit name="rgba" mode="assign"><const>rgb</const></edit>
</match>
</fontconfig>
EOF
fc-cache -f
/etc/fonts/conf.d/50-user.conf includes ~/.config/fontconfig/conf.d first and ~/.config/fontconfig/fonts.conf second. So the drop-in loads after Omarchy's package rule 50-omarchy.conf and before the monospace block that omarchy font set writes. Leave fonts.conf to Omarchy from now on.
If you track dotfiles, keep fonts.conf out of them, because Omarchy rewrites it on every font change.
Plain Arch: nothing rewrites fonts.conf, so this does not apply.
Verify
omarchy font set "$(fc-match -f '%{family[0]}' monospace)"
ls ~/.config/fontconfig/conf.d/60-my-rules.conf
fc-conflist | grep 60-my-rules
The drop-in survives the font set and fc-conflist lists it as active.