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

Powerline glyph's render incorrectly (sometimes) #1922

New Issue
Closed
opened 2026-01-30 22:42:01 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 22:42:01 +00:00
Owner
Copy Link

Originally created by @A-Lamia on GitHub (Jun 22, 2019).

Environment

Windows build number: [Microsoft Windows [Version 10.0.18362.175]
Windows Terminal version (if applicable): First Preview version;

Font's used
Fira Code - (Ligature)
FuraCode NF - (Ligature)
Hack
Hack NF

Steps to reproduce

Happened after PC restart tested out other fonts to see if it would fix and restarted PC again.

After more testing, this seems to be 2 bugs, the first is setting "alwaysShowTabs" to true will cause Glyphs to break setting it to false fixes the issue. this bug only seems to happen if set to true on system restarts. It is about a 25% chance of reproducing it this number may change for some.

The Ligatures not rendering properly is only with the Nerd Font variant of the ligature fonts, standard versions work fine. This ended up being a separate issue from the one above after more testing.

Expected behavior

ligatures and glyph's rendering correctly

Glyphs should render the same regardless of if "alwaysShowTabs" is set to true or false.

Actual behavior

Glyphs are not connecting and ligatures are not working the first character typed will also be hidden by the triangle glyph.

Glyphs not rendering correctly and overlapping characters that come right after.
Terminals

Originally created by @A-Lamia on GitHub (Jun 22, 2019). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [Microsoft Windows [Version 10.0.18362.175] Windows Terminal version (if applicable): First Preview version; Font's used Fira Code - (Ligature) FuraCode NF - (Ligature) Hack Hack NF ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> ~Happened after PC restart tested out other fonts to see if it would fix and restarted PC again.~ After more testing, this seems to be 2 bugs, the first is setting `"alwaysShowTabs" ` to true will cause Glyphs to break setting it to `false` fixes the issue. this bug only seems to happen if set to `true` on system restarts. It is about a 25% chance of reproducing it this number may change for some. The Ligatures not rendering properly is only with the [Nerd Font](http://nerdfonts.com/) variant of the ligature fonts, standard versions work fine. This ended up being a separate issue from the one above after more testing. # Expected behavior ~ligatures and glyph's rendering correctly~ Glyphs should render the same regardless of if `"alwaysShowTabs"` is set to `true` or `false`. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? --> ~Glyphs are not connecting and ligatures are not working the first character typed will also be hidden by the triangle glyph.~ Glyphs not rendering correctly and overlapping characters that come right after. ![Terminals](https://i.imgur.com/aTZRKGk.png?raw=true)
claunia added the Area-RenderingIssue-BugResolution-DuplicateProduct-Terminal labels 2026-01-30 22:42:01 +00:00
claunia commented 2026-01-30 22:42:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 24, 2019):

The Ligatures not rendering properly is only with the Nerd Font variant of the ligature fonts,

I'm going to go out on a limb and say, "I'm going to go out on a limb and say it's the font."

@DHowett-MSFT commented on GitHub (Jun 24, 2019): > The Ligatures not rendering properly is only with the [Nerd Font](http://nerdfonts.com/) variant of the ligature fonts, I'm going to go out on a limb and say, "I'm going to go out on a limb and say it's the font."
claunia commented 2026-01-30 22:42:02 +00:00
Author
Owner
Copy Link

@neo-clon commented on GitHub (Jun 25, 2019):

Is'nt the font, you can reproduce with this steps

  1. Open the terminal with Consolas font
  2. Switch the profile font with any on Nerdfont (I try with, meslo, hack and Hasklug)
    (In this moment the terminal and fonts looks awesome)
  3. Restart the terminal and see how loss the ligatures

image
image
image

@neo-clon commented on GitHub (Jun 25, 2019): Is'nt the font, you can reproduce with this steps 1. Open the terminal with Consolas font 2. Switch the profile font with any on Nerdfont (I try with, meslo, hack and Hasklug) (In this moment the terminal and fonts looks awesome) 3. Restart the terminal and see how loss the ligatures ![image](https://user-images.githubusercontent.com/12282168/60122366-a6017c00-974a-11e9-882f-6f851b488731.png) ![image](https://user-images.githubusercontent.com/12282168/60122377-ad288a00-974a-11e9-8d52-a1d524a26214.png) ![image](https://user-images.githubusercontent.com/12282168/60122383-b1ed3e00-974a-11e9-9fb8-ca6e3dc166cd.png)
claunia commented 2026-01-30 22:42:02 +00:00
Author
Owner
Copy Link

@MikeBairdRocks commented on GitHub (Jun 26, 2019):

Yes this is a bug IMO. Every other terminal I try on windows works with these fonts, wsl and zsh. Hyperjs, cmdr, Terminus...etc.

@MikeBairdRocks commented on GitHub (Jun 26, 2019): Yes this is a bug IMO. Every other terminal I try on windows works with these fonts, wsl and zsh. Hyperjs, cmdr, Terminus...etc.
claunia commented 2026-01-30 22:42:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 2, 2019):

Oh yea those aren't ligatures. Those are powerline characters.

It's curious to me that if you start with consolas, then switch to FuraCode NF it breaks. That's probably a bug.

@zadjii-msft commented on GitHub (Jul 2, 2019): Oh yea those aren't ligatures. Those are _powerline_ characters. It's curious to me that if you start with consolas, then switch to FuraCode NF it breaks. That's probably a bug.
claunia commented 2026-01-30 22:42:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 2, 2019):

Wait no this is already #633

@zadjii-msft commented on GitHub (Jul 2, 2019): Wait no this is already #633
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-Rendering 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#1922
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?