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

Font Selection Not Persisting on Launch / Requires Saving Settings for Change to Take Effect #21245

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

Originally created by @JanusDC on GitHub (Feb 14, 2024).

Windows Terminal version

1.18.10301.0

Windows build number

Windows 11 Pro 23H2 (build number 22631.3085)

Other Software

Droid Sans Mono for Powerline font version 1.00 build 113.

Steps to reproduce

  1. Install the "Droid Sans Mono for Powerline" font (verify installation in the Windows Fonts folder).
  2. Open Windows Terminal settings.
  3. Under either the "Defaults" profile or a custom profile, set the fontFace property to "Droid Sans Mono for Powerline".
  4. Save settings and close Windows Terminal.
  5. Reopen Windows Terminal and observe the font error.
  6. Open settings again and without making changes, press "Save." The font loads correctly.

Expected Behavior

Upon launching Windows Terminal, the configured default font or profile-specific font should load correctly without any additional actions.

Actual Behavior

The selected font is not recognized at launch, displaying an error message similar to "The selected font 'Droid Sans Mono for Powerline' cannot be found." To make the font work, I must open the Windows Terminal settings and press "Save", even though no actual changes were made.

Originally created by @JanusDC on GitHub (Feb 14, 2024). ### Windows Terminal version 1.18.10301.0 ### Windows build number Windows 11 Pro 23H2 (build number 22631.3085) ### Other Software Droid Sans Mono for Powerline font version 1.00 build 113. ### Steps to reproduce 1. Install the "Droid Sans Mono for Powerline" font (verify installation in the Windows Fonts folder). 2. Open Windows Terminal settings. 3. Under either the "Defaults" profile or a custom profile, set the fontFace property to "Droid Sans Mono for Powerline". 4. Save settings and close Windows Terminal. 5. Reopen Windows Terminal and observe the font error. 6. Open settings again and without making changes, press "Save." The font loads correctly. ### Expected Behavior Upon launching Windows Terminal, the configured default font or profile-specific font should load correctly without any additional actions. ### Actual Behavior The selected font is not recognized at launch, displaying an error message similar to "The selected font 'Droid Sans Mono for Powerline' cannot be found." To make the font work, I must open the Windows Terminal settings and press "Save", even though no actual changes were made.
claunia added the Issue-BugResolution-DuplicateProduct-Terminal labels 2026-01-31 07:37: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-Bug Product-Terminal 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#21245
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?