starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Feature Request: Update fontFace to support multiple fonts #7784

New Issue
Open
opened 2026-01-31 01:12:34 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 01:12:34 +00:00
Owner
Copy Link

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:34 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7784
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?