Repository navigation
Stop mutating ~/.config terminal files in omarchy font set
#7013
infogulch
started this conversation in
Suggestions
Replies: 1 comment
|
I'm also affected by this problem. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Font is Omarchy-managed state, but omarchy font set currently seds
~/.config/{ghostty,alacritty,kitty,foot}. Those are the user’s files, Omarchy should not rewrite them.That causes:
Proposal
Write the active font under
~/.local/state/omarchy/current/font/(sibling ofcurrent/theme). Shipped terminal templates only include / import / config-file that snippet, the same way they already pull theme colors.font setupdates the generated files andfonts.confonly.Alternative: bake the active font into the existing current/theme/ snippets and have font set regenerate those instead of adding
current/font/. Same “don’t touch ~/.config” outcome, no new includes. This is not my preference: font changes shouldn’t run through the theme switcher, and mixing font into the color pack couples two axes in a script that is already doing too much.Related: #3555, #4818, #6957
All reactions