Setting a font in settings.json #8714

Closed
opened 2026-01-31 01:36:13 +00:00 by claunia · 5 comments
Owner

Originally created by @jromero2k on GitHub (Jun 1, 2020).

Environment

Windows build number: Version 10.0.18363.778
Windows Terminal version (if applicable): 1.0.1401.0

Steps to reproduce

  1. Install ttc-iosevka-curly-3.1.0.zip fonts in Windows
  2. Verify it works properly in any other app
  3. In settings.json, set "fontFace": "Iosevka Term Curly Light"

Expected behavior

Iosevka Term Curvy Light is selected as active font, or some kind of error is reported so user can know what's that Terminal didn't like

Actual behavior

Terminal reverts to the default (non-ligature) font, without any explanation (or logging that I know of)

Originally created by @jromero2k on GitHub (Jun 1, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Windows build number: Version 10.0.18363.778 Windows Terminal version (if applicable): 1.0.1401.0 # Steps to reproduce 1. Install `ttc-iosevka-curly-3.1.0.zip` fonts in Windows 2. Verify it works properly in any other app 3. In `settings.json`, set `"fontFace": "Iosevka Term Curly Light"` # Expected behavior `Iosevka Term Curvy Light` is selected as active font, or some kind of error is reported so user can know what's that Terminal didn't like # Actual behavior Terminal reverts to the default (non-ligature) font, without any explanation (or logging that I know of)
claunia added the Resolution-Duplicate label 2026-01-31 01:36:13 +00:00
Author
Owner

@skyline75489 commented on GitHub (Jun 1, 2020):

The reason why it uses the default font would likely be that the font name is not recognized. Yeah you're right. There's currently no explanation when this happens. Seems a little confusing.

@skyline75489 commented on GitHub (Jun 1, 2020): The reason why it uses the default font would likely be that the font name is not recognized. Yeah you're right. There's currently no explanation when this happens. Seems a little confusing.
Author
Owner

@jromero2k commented on GitHub (Jun 1, 2020):

As far as I can tell, Iosevka Term Curly Light is the proper name for the font, at least as reported by Settings|Font settings in Windows..

Having "fontFace": "Iosevka Term Curly" "fontWeight": "200" like in VSCode would be even better, but that's not available (yet?)

@jromero2k commented on GitHub (Jun 1, 2020): As far as I can tell, `Iosevka Term Curly Light` is the proper name for the font, at least as reported by `Settings|Font settings` in Windows.. Having ` "fontFace": "Iosevka Term Curly" "fontWeight": "200" ` like in VSCode would be even better, but that's not available (yet?)
Author
Owner

@WSLUser commented on GitHub (Jun 2, 2020):

fontWeight will be in Preview (it's in master if you want to build it).

@WSLUser commented on GitHub (Jun 2, 2020): fontWeight will be in Preview (it's in master if you want to build it).
Author
Owner

@DHowett commented on GitHub (Jun 5, 2020):

I believe the root of the issue is that we specify font family names and call them font faces. For now, fontFace: Iosevka Term Curly should suffice, and font weight will come out soon. For fixing the root cause, /dup #1163.

@DHowett commented on GitHub (Jun 5, 2020): I believe the root of the issue is that we specify font _family_ names and call them font _faces_. For now, `fontFace: Iosevka Term Curly` should suffice, and font weight will come out soon. For fixing the root cause, /dup #1163.
Author
Owner

@ghost commented on GitHub (Jun 5, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 5, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8714