Repository navigation
omarchy display text size should scale the terminal font from the user's own size, not a hardcoded 9pt anchor #9767
Replies: 1 comment
|
This matches a consistency problem we investigated on Omarchy 4.0.4-1. The installed In our setup, the preferred terminal text is smaller than application UI text. Preserving that choice while adjusting the bar and monitor scale made the desktop more comfortable. Equal numeric font sizes are not the goal: terminal/code text, UI labels, and reading text serve different roles, and apps expose sizes in different units. I support preserving the user's terminal anchor, as proposed here. It would also help to expose separate shell/bar and application-text adjustments, or clearly explain which roles the combined control changes. A small regression check could verify that changing the global control and returning it to the original value restores a user's custom terminal size, across the supported terminal backends and theme/font changes. There is a related Electron concern: at a fixed 1.25 monitor scale, an isolated native-Wayland Electron 43.6.0 probe reports DPR 1.25 with the GTK text multiplier at 1.0, and 1.5234375 with it at 1.2222. I added the reproduction to #8574. This suggests that the GTK leg of the combined control deserves separate validation as well. The local policy we tested keeps per-monitor scale as a hardware-specific setting, preserves terminal and bar preferences, and uses explicit app text roles plus native theme settings where available. The particular font sizes we chose are personal preferences; the reusable part is preserving those preferences and avoiding unintended multiplication of scale factors. |
Uh oh!
There was an error while loading. Please reload this page.
What happens
omarchy display text size <px>drives the shell base-size, the GTK text-scaling-factor and the terminal font size in lockstep. For the terminal it writes an absolute point size derived from a hardcoded anchor, so any terminal size the user chose themselves is discarded on the first text-size change — and never comes back, because every later change re-derives from the same constant rather than scaling what the user picked.From
omarchy-display-text-size:Why this one leg stands out
The other two legs already respect what the user has configured:
[font] base-sizeis written as an override in~/.config/omarchy/shell.tomlthat layers on top of the active theme, so it survives theme switches.gtk_font_pt(), so the result lands on a whole point size for whateverfont-namethey have set.The terminal is the only one of the three that ignores the value already in the config and overwrites it with a constant-derived one.
Steps to reproduce
This is not foot-specific — alacritty, kitty and ghostty get the same absolute rewrite in
set_terminal_size().Suggestion
Scale the terminal font from the user's own anchor instead of a constant:
where
user_anchor_ptdefaults to 9 (identical behaviour for anyone who never touched their terminal config) but is captured from the terminal config the first time the command runs — e.g. stored next to[font] base-sizein~/.config/omarchy/shell.toml, or derived on the fly ascurrent_pt / term_pt_for(current_px)before writing the new value.That keeps the one-knob-drives-everything design intact while letting a deliberately larger or smaller terminal ride along proportionally, the way the shell and GTK legs already do.
As a smaller alternative, an env var or a key in
shell.tomlto set the terminal anchor would also solve it — right now there is no knob at all, and notext-sizehook to correct it from either.Related
omarchy font setseparately resets foot's size to a hardcoded 9.System
All reactions