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 in Nerd Fonts are rendered with wrong widths #15898

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

Originally created by @benfowler on GitHub (Nov 16, 2021).

Windows Terminal version

1.12.2931.0

Windows build number

10.0.19042.0

Other Software

  • Font: CaskaydiaCove Nerd Font

Steps to reproduce

  1. Open Windows Terminal Preview with a clean configuration
  2. Obtain the "CaskaydiaCove Nerd Font" (patched stock Windows Terminal font), and install it via choco install cascadia-code-nerd-font
  3. Output the characters onto the console. I've made the attached text file to do a minimal reproduction of this issue: break_tmux_nf_glyph_broken_under_msterm.txt
    • nf-mdi-play (f909) and nf-mdi-stop (f9da). Character width, cell width get confused, especially depending on what character follows 'odd' character, and how many there are on a given line.
    • NOTE: Other glyphs, e.g.  nf-custom-folder-github (e5fd) render correctly
    • For more information on Nerd Font glyphs, see the Nerd Font Cheat Sheet

Expected Behavior

Correct rendering of widths of Nerd Font glyphs, as far as I can tell.

screenshot-nf-glyphs-correct-alacritty

This screenshot has been generated using Alacritty, but I also tried this out on Kitty and Mac Terminal (MacOS) and got the same expected behaviour.

I've added a second screenshot of Windows Terminal Preview rendering the same text file, with **Cascadia Mono"", to demonstrate how the ostensibly-correct rendering of these glyphs appears to adhere to what Windows Terminal would do with the stock (unpatched) font's glyphs for the same code points:

screenshot-nf-glyphs-STOCK-Cascadia-winterm

Actual Behavior

Result of outputting test text file in Windows Terminal:

screenshot-nf-glyphs-wrong-winterm

Even if the characters are 'wide' in the unpatched font, these glyphs are not rendered wide in patched ('Nerd Font') fonts.

Good (Alacritty and other terminal emulators):

bar-good-alacritty

Bad (Windows Terminal Preview):

bar-bad-windows-terminal-pre

Originally created by @benfowler on GitHub (Nov 16, 2021). ### Windows Terminal version 1.12.2931.0 ### Windows build number 10.0.19042.0 ### Other Software * Font: CaskaydiaCove Nerd Font ### Steps to reproduce 1. Open Windows Terminal Preview with a clean configuration 2. Obtain the "CaskaydiaCove Nerd Font" (patched stock Windows Terminal font), and install it via `choco install cascadia-code-nerd-font` 3. Output the characters onto the console. I've made the attached text file to do a minimal reproduction of this issue: [break_tmux_nf_glyph_broken_under_msterm.txt](https://github.com/microsoft/terminal/files/7550146/break_tmux_nf_glyph_broken_under_msterm.txt) - `nf-mdi-play` (f909) and `nf-mdi-stop` (f9da). Character width, cell width get confused, especially depending on what character follows 'odd' character, and how many there are on a given line. - **NOTE**: Other glyphs, e.g.  `nf-custom-folder-github` (e5fd) **render correctly** - For more information on Nerd Font glyphs, see the [Nerd Font Cheat Sheet](https://www.nerdfonts.com/cheat-sheet) ### Expected Behavior Correct rendering of widths of Nerd Font glyphs, as far as I can tell. ![screenshot-nf-glyphs-correct-alacritty](https://user-images.githubusercontent.com/1638317/142074933-5d9deceb-0507-4355-b05c-c50b063998fe.png) This screenshot has been generated using Alacritty, but I also tried this out on Kitty and Mac Terminal (MacOS) and got the same expected behaviour. I've added a second screenshot of Windows Terminal Preview rendering the same text file, with **Cascadia Mono"", to demonstrate how the ostensibly-correct rendering of these glyphs appears to adhere to what Windows Terminal would do with the stock (unpatched) font's glyphs for the same code points: ![screenshot-nf-glyphs-STOCK-Cascadia-winterm](https://user-images.githubusercontent.com/1638317/142075205-35bd4452-8997-4ec1-af6e-cd32b629a205.png) ### Actual Behavior Result of outputting test text file in Windows Terminal: ![screenshot-nf-glyphs-wrong-winterm](https://user-images.githubusercontent.com/1638317/142075639-5f075e27-9983-40a9-b123-ab9080daf23e.png) Even if the characters are 'wide' in the unpatched font, these glyphs are not rendered wide in patched ('Nerd Font') fonts. Good (Alacritty and other terminal emulators): ![bar-good-alacritty](https://user-images.githubusercontent.com/1638317/142076233-8cf1eeb3-8fcc-4ac2-a8a5-af7d385c24a9.png) Bad (Windows Terminal Preview): ![bar-bad-windows-terminal-pre](https://user-images.githubusercontent.com/1638317/142076259-60810630-088c-4015-944d-6b702c6f5a3e.png)
claunia added the Resolution-DuplicateProduct-TerminalArea-Fonts labels 2026-01-31 04:51:38 +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 Area-Fonts 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#15898
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?