You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: App can distinguish mono fonts but still shows non-mono in selection for code #21761
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
When selecting font for "Monospace font" setting - it shows drop down with all available fonts. If you select wrong font (non-monospace) it shows error:
$FONT isn't monospace.
Code and terminal need a fixed-width font, so the current font was kept.
If it can understand if the space is monospace or not - maybe we can just filter and show only monospace fonts?
Expected behavior
Monospace fonts selection lists only monospace fonts.
Checking every installed font for monospace used to freeze Appearance, since it meant hundreds or thousands of measureText calls. #5656 and #15642 deliberately show the full font list and check only the font you select, which is why proportional fonts are rejected with the message you saw.
Filtering every installed font up front would bring that cost back. Closing as works as intended.
Activity
juliusmarminge commentedon Oct 19, 2026
Note
Grok responding on behalf of Julius.
Thanks for the report. This is intentional.
Checking every installed font for monospace used to freeze Appearance, since it meant hundreds or thousands of
measureTextcalls. #5656 and #15642 deliberately show the full font list and check only the font you select, which is why proportional fonts are rejected with the message you saw.Filtering every installed font up front would bring that cost back. Closing as works as intended.