Allow the terminal to adhere to the system font.

Open
#4,227 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli, desktop

Research direction

No files, tests, or entry points are named in the issue. Start by locating the terminal's font preference handling and the platform-specific system font settings; done means the terminal updates to follow the system font rather than relying on monospace, serif, or sans-serif aliases.

Written by the indexing model from the issue text.

Description

area:ui-framework enhancement triaged
Discord username (optional)

discord.com/users/798720532848705576 [^1]

Describe the solution you'd like?

As aforestated:

Allow the terminal to adhere to the system font.

Is your feature request related to a problem? Please describe.

When my system font changes, my terminal's does not. I have no reason for these preferences to be separate.

Additional context

This differs from https://github.com/warpdotdev/Warp/issues/4224#issue-2149655659 in that font aliases are a workaround, whereas what this issue proposes is the correct solution to this issue. Specifically, the existent font aliases are inadequate because they are font type-specific, being solely monospace, serif, or sans-serif. Although an alias could be created by the DE/OS which contains the defined default font, but no distribution does that, and I do not intend to.

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

[^1]: #L437 of a .MD file at gitlab.com/rokejulianlockhart/rokejulianlockhart/-/blob/8281225398011257df4d65637fff42796ce7c781

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.