Repository navigation
Conversation
The settings popover only exposed font size, so switching to an installed programming font meant hand-editing localStorage. Add a font family picker with common monospace presets (each keeping CJK and emoji fallbacks) plus letter spacing and line height steppers, applied live to every tab. Line height is clamped to at least 1 because xterm throws below that, and letter spacing is kept to whole pixels as xterm documents. A family stored outside the presets shows up as "Custom" instead of being misreported.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The settings popover only exposes font size, so using an installed programming font (or loosening dense glyphs) meant hand-editing
localStorage. This adds three settings next to Font Size, applied live to every tab and persisted with the other prefs:letterSpacing.lineHeight < 1.Stored values go through the same validation as the existing prefs in
loadPrefs()(clamped; invalid values fall back to the defaults), and the README settings table is updated.Testing
npm run typecheckandnpm run buildpass.npm test:resize reaches the PTYfails, anda dropped connection keeps the shell alive…fails intermittently, on unmodifiedmaintoo in my environment (Debian 13, Node 24). This change only touches the frontend.