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

Some glyphs do not display correctly until the settings are saved. #19407

New Issue
Closed
opened 2026-01-31 06:42:21 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:42:21 +00:00
Owner
Copy Link

Originally created by @igorkuzuro on GitHub (Feb 18, 2023).

Windows Terminal version

Build from current source code

Windows build number

10.0.25295.0

Other Software

PowerShell core 7.3.2
Oh My Posh version 14.7.0
Delugia font (https://github.com/adam7/delugia-code)

Steps to reproduce

I use Oh My Posh segment which using character \uf199f (Timer Sand Complete or nf-md-timer_sand_complete from https://www.nerdfonts.com/cheat-sheet) This character did not display correctly until I just open settings and press Save...
After the terminal is restarted, the error reappears.

Terminal using Delugia font as default and for Powershell Core

See screenshots: upper part before Save settings, lower part - after.

ss

Expected Behavior

Glyph rendered as Timer Sand Complete

Actual Behavior

Glyph rendered as "placeholder" character

Originally created by @igorkuzuro on GitHub (Feb 18, 2023). ### Windows Terminal version Build from current source code ### Windows build number 10.0.25295.0 ### Other Software PowerShell core 7.3.2 Oh My Posh version 14.7.0 Delugia font (https://github.com/adam7/delugia-code) ### Steps to reproduce I use Oh My Posh segment which using character \uf199f (Timer Sand Complete or nf-md-timer_sand_complete from https://www.nerdfonts.com/cheat-sheet) This character did not display correctly until I just open settings and press Save... After the terminal is restarted, the error reappears. Terminal using Delugia font as default and for Powershell Core See screenshots: upper part before Save settings, lower part - after. ![ss](https://user-images.githubusercontent.com/1778999/219884888-e93ccff8-d0cb-414f-bbf0-88eca63ca11f.jpg) ### Expected Behavior Glyph rendered as Timer Sand Complete ### Actual Behavior Glyph rendered as "placeholder" character
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:42:21 +00:00
claunia commented 2026-01-31 06:42:22 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 20, 2023):

Did you recently update your font? This could be a corruption in the font cache service. You could try restarting the service in PowerShell, as an Administrator, using this command:

Restart-Service FontCache

Did you install this font for your current user only or for all users (%LocalAppData%\Microsoft\Windows\Fonts vs. C:\Windows\Fonts)? Or does the font potentially exist in both directories in different versions? Using the latter exclusively might be more robust.

@lhecker commented on GitHub (Feb 20, 2023): Did you recently update your font? This could be a corruption in the font cache service. You could try restarting the service in PowerShell, as an Administrator, using this command: ```pwsh Restart-Service FontCache ``` Did you install this font for your current user only or for all users (`%LocalAppData%\Microsoft\Windows\Fonts` vs. `C:\Windows\Fonts`)? Or does the font potentially exist in both directories in different versions? Using the latter exclusively might be more robust.
claunia commented 2026-01-31 06:42:22 +00:00
Author
Owner
Copy Link

@igorkuzuro commented on GitHub (Feb 20, 2023):

Did you recently update your font? This could be a corruption in the font cache service. You could try restarting the service in PowerShell, as an Administrator, using this command:

Restart-Service FontCache

Did you install this font for your current user only or for all users (%LocalAppData%\Microsoft\Windows\Fonts vs. C:\Windows\Fonts)? Or does the font potentially exist in both directories in different versions? Using the latter exclusively might be more robust.

Yes, after install the font for all users, the problem disappeared.

@igorkuzuro commented on GitHub (Feb 20, 2023): > Did you recently update your font? This could be a corruption in the font cache service. You could try restarting the service in PowerShell, as an Administrator, using this command: > > ```powershell > Restart-Service FontCache > ``` > > Did you install this font for your current user only or for all users (`%LocalAppData%\Microsoft\Windows\Fonts` vs. `C:\Windows\Fonts`)? Or does the font potentially exist in both directories in different versions? Using the latter exclusively might be more robust. Yes, after install the font for all users, the problem disappeared.
claunia commented 2026-01-31 06:42:22 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 22, 2023):

Awesome! We're gonna close this out and mark it as a /dup of #3257

@carlos-zamora commented on GitHub (Feb 22, 2023): Awesome! We're gonna close this out and mark it as a /dup of #3257
claunia commented 2026-01-31 06:42:23 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 22, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Feb 22, 2023): 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.
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 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#19407
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?