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

Nerd Font Icons Not Displaying Right Size in Windows Terminal Preview #18896

New Issue
Closed
opened 2026-01-31 06:27:30 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:27:30 +00:00
Owner
Copy Link

Originally created by @qennenat on GitHub (Nov 14, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22621.0

Other Software

Steps to reproduce

  1. First download and install Windows Terminal Preview from the Microsoft Store. (Microsoft Store Page of Windows Terminal Preview)
  2. Download and install Powershell Preview by downloading the .msi from the Powershell GitHub page. Powershell GitHub.
  3. Install Oh-My-Posh via Winget. To do so...
    • Open a PowerShell Preview prompt in Windows Terminal Preview.
    • Run the following command: winget install JanDeDobbeleer.OhMyPosh -s winget.
    • Now configure Oh My Posh to use the "Clean Detailed" theme. To do so, run the following command: oh-my-posh init pwsh --config "https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/clean-detailed.omp.json" | Invoke-Expression.
  4. Now open another Powershell Preview prompt in Windows Terminal.
    • Now configure Oh My Posh to use the "Clean Detailed" theme. To do so, run the following command: oh-my-posh init pwsh --config "https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/clean-detailed.omp.json" | Invoke-Expression.
  5. Compare the Oh My Posh prompt on Windows Terminal to the Oh My Posh prompt on Windows Terminal Preview.

(!) Note

The Oh My Posh theme used, terminal font used, or even font size, has no direct effect on this bug in Windows Terminal Preview. This bug persists across all Oh My Posh themes, set terminal fonts, etc.

Take a particular look at the following character/gylphs...

  • nf-mdi-microsoft (f871)
  • nf-oct-terminal (f489)
  • nf-mdi-memory (f85a)
  • nf-mdi-heart (f7d0)
  • nf-mdi-home (f7db)

I recommend using nerdfonts.com/cheat-sheet to see these icons.

Expected Behavior

I am expecting all Nerd Fonts' characters/glyphs to be displayed in the correct size. In other words, I am expecting to them to be displayed as seen correctly in Windows Terminal.

Refer to the image below. Notice how in Windows Terminal, all the characters/glyphs are displayed in the same size. In contrast, Windows Terminal Preview displays the characters/glyphs smaller.

Windows Terminal
image

Actual Behavior

Refer to the images below. Notice how in Windows Terminal, all the characters/glyphs are displayed in the same size. In contrast, Windows Terminal Preview displays some of the characters/glyphs smaller.

Windows Terminal
image
Windows Terminal Preview
image

Originally created by @qennenat on GitHub (Nov 14, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22621.0 ### Other Software - **Powershell Preview** (Version: 7.3.0-rc1) - [GitHub](https://github.com/PowerShell/PowerShell) - **Oh-My-Posh** (Version: 12.13.3) - [GitHub](https://github.com/JanDeDobbeleer/oh-my-posh) - [Website](https://ohmyposh.dev/) - **Caskaydia Cove Nerd Font** - [Website](https://www.nerdfonts.com/font-downloads) ### Steps to reproduce 1. First download and install **Windows Terminal Preview** from the Microsoft Store. ([Microsoft Store Page of Windows Terminal Preview](https://www.microsoft.com/store/productId/9N8G5RFZ9XK3)) 2. Download and install **Powershell Preview** by downloading the .msi from the Powershell GitHub page. [Powershell GitHub](https://github.com/PowerShell/PowerShell). 3. Install **Oh-My-Posh** via Winget. To do so... - Open a **PowerShell Preview** prompt in **Windows Terminal Preview**. - Run the following command: `winget install JanDeDobbeleer.OhMyPosh -s winget`. - Now configure **Oh My Posh** to use the "_Clean Detailed_" theme. To do so, run the following command: `oh-my-posh init pwsh --config "https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/clean-detailed.omp.json" | Invoke-Expression`. 4. Now open another **Powershell Preview** prompt in **Windows Terminal**. - Now configure Oh My Posh to use the "Clean Detailed" theme. To do so, run the following command: `oh-my-posh init pwsh --config "https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/clean-detailed.omp.json" | Invoke-Expression`. 5. Compare the **Oh My Posh** prompt on **Windows Terminal** to the Oh My Posh prompt on **Windows Terminal Preview**. ### (!) Note The **Oh My Posh** theme used, terminal font used, or even font size, has _no_ direct effect on this bug in **Windows Terminal Preview**. This bug persists across _all_ **Oh My Posh** themes, set terminal fonts, etc. Take a particular look at the following character/gylphs... - nf-mdi-microsoft (f871) - nf-oct-terminal (f489) - nf-mdi-memory (f85a) - nf-mdi-heart (f7d0) - nf-mdi-home (f7db) I recommend using [nerdfonts.com/cheat-sheet](https://www.nerdfonts.com/cheat-sheet) to see these icons. ### Expected Behavior I am expecting _all_ Nerd Fonts' characters/glyphs to be displayed in the correct size. In other words, I am expecting to them to be displayed as seen correctly in **Windows Terminal**. Refer to the image below. Notice how in **Windows Terminal**, all the characters/glyphs are displayed in the same size. In contrast, **Windows Terminal Preview** displays the characters/glyphs smaller. **Windows Terminal** ![image](https://user-images.githubusercontent.com/43337293/201743744-80886837-5cb0-4d34-bd4f-4a12ce7b8627.png) ### Actual Behavior Refer to the images below. Notice how in **Windows Terminal**, all the characters/glyphs are displayed in the same size. In contrast, **Windows Terminal Preview** displays some of the characters/glyphs smaller. **Windows Terminal** ![image](https://user-images.githubusercontent.com/43337293/201743744-80886837-5cb0-4d34-bd4f-4a12ce7b8627.png) **Windows Terminal Preview** ![image](https://user-images.githubusercontent.com/43337293/201744169-ca52f0bb-f071-44ea-b267-4ad869a0b73f.png)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:27:31 +00:00
claunia commented 2026-01-31 06:27:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 14, 2022):

Thanks for the report!

This is a /duplicate of #14022, which is rooted in our renderer being more strict about font widths whereas Nerd Fonts somewhat expects glyphs to be drawn outside their cells. 😄

@DHowett commented on GitHub (Nov 14, 2022): Thanks for the report! This is a /duplicate of #14022, which is rooted in our renderer being more strict about font widths whereas Nerd Fonts somewhat expects glyphs to be drawn _outside_ their cells. :smile:
claunia commented 2026-01-31 06:27:32 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 14, 2022):

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 (Nov 14, 2022): 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!
claunia commented 2026-01-31 06:27:32 +00:00
Author
Owner
Copy Link

@qennenat commented on GitHub (Nov 14, 2022):

Thanks for the report!

This is a /duplicate of #14022, which is rooted in our renderer being more strict about font widths whereas Nerd Fonts somewhat expects glyphs to be drawn outside their cells. 😄

Oh okay, thank you! Apologies for the duplicate report. Was trying to find this issue beforehand. Take care. 😄

@qennenat commented on GitHub (Nov 14, 2022): > Thanks for the report! > > This is a /duplicate of #14022, which is rooted in our renderer being more strict about font widths whereas Nerd Fonts somewhat expects glyphs to be drawn _outside_ their cells. 😄 Oh okay, thank you! Apologies for the duplicate report. Was trying to find this issue beforehand. Take care. 😄
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#18896
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?