Feature Request: Update fontFace to support multiple fonts #7787

Closed
opened 2026-01-31 01:12:37 +00:00 by claunia · 2 comments
Owner

Originally created by @anjc on GitHub (Apr 29, 2020).

Description of the new feature/enhancement

I would like to be able to list multiple fonts in settings.json's fontFace property, so if the first font isn't available Terminal can attempt to choose from a series of fallbacks - which is what web developers [and VS Code users] do when storing multiple fonts in the font-family property.

This would be useful for people who sync Windows Terminal's settings across multiple devices (in my case, by fsutil hardlinking settings.json to a file in OneDrive) or share their configs with others, so the end-user can experience the modifications as-intended.

This would also allow Windows Terminal to have multiple fallbacks, like fontFace: "Cascadia Mono, Consolas", when a user enters an invalid font-name.

Proposed technical implementation details (optional)

I would recommend mirroring VS Code's implementation of this in their settings.json file: font names are separated by commas, with priority going from left-to-right.

Originally created by @anjc on GitHub (Apr 29, 2020). # Description of the new feature/enhancement I would like to be able to list multiple fonts in `settings.json`'s `fontFace` property, so if the first font isn't available Terminal can attempt to choose from a series of fallbacks - which is what web developers [and VS Code users] do when storing multiple fonts in the [`font-family`](https://developer.mozilla.org/en-US/docs/Web/CSS/font-family) property. <!-- This is what such a setting looks like in VS Code (interface and json). ![image](https://user-images.githubusercontent.com/36517378/80565878-992f6380-89bf-11ea-82c0-ddcceb8d3139.png) ![image](https://user-images.githubusercontent.com/36517378/80565865-92085580-89bf-11ea-9f42-b740c1ca1963.png) --> This would be useful for people who sync Windows Terminal's settings across multiple devices (in my case, by [`fsutil`](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-hardlink) hardlinking settings.json to a file in OneDrive) or share their configs with others, so the end-user can experience the modifications as-intended. This would also allow Windows Terminal to have multiple fallbacks, like `fontFace: "Cascadia Mono, Consolas"`, when a user enters an invalid font-name. # Proposed technical implementation details (optional) I would recommend mirroring VS Code's implementation of this in their `settings.json` file: font names are separated by commas, with priority going from left-to-right.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:12:37 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 29, 2020):

Thanks for the request! This is a /dupe of #2664.

@DHowett-MSFT commented on GitHub (Apr 29, 2020): Thanks for the request! This is a /dupe of #2664.
Author
Owner

@ghost commented on GitHub (Apr 29, 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 (Apr 29, 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#7787