starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Subset of Ligatures not working when using Powershell #2075

New Issue
Closed
opened 2026-01-30 22:46:09 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:46:09 +00:00
Owner
Copy Link

Originally created by @LoZeno on GitHub (Jun 24, 2019).

Some ligatures don't work when using Powershell or Powershell 6, they do work correctly when using WSL Ubuntu instead.

Environment

Microsoft Windows 10

Windows build number: [run "ver" at a command prompt]
[Version 10.0.18362.175]
Windows Terminal version (if applicable):
0.2.1715.0
Any other software?
Fira Code fonts

Steps to reproduce

Start Windows Terminal with a Powershell prompt;
type this sequence of characters:
<= <> >= != => <==

Open a tab with WSL Ubuntu, and type the same sequence of characters:
<= <> >= != => <==

Expected behavior

all the ligatures should work the same way in powershell and WSL ubuntu .

Actual behavior

In the powershell tab, the ligatures of <= and >= do not work, the rest does.
image

In the WSL Ubuntu tab, all the ligatures work
image

Originally created by @LoZeno on GitHub (Jun 24, 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. --> Some ligatures don't work when using Powershell or Powershell 6, they do work correctly when using WSL Ubuntu instead. # Environment Microsoft Windows 10 ```none Windows build number: [run "ver" at a command prompt] [Version 10.0.18362.175] Windows Terminal version (if applicable): 0.2.1715.0 Any other software? Fira Code fonts ``` # Steps to reproduce Start Windows Terminal with a Powershell prompt; type this sequence of characters: <= <> >= != => <== Open a tab with WSL Ubuntu, and type the same sequence of characters: <= <> >= != => <== # Expected behavior all the ligatures should work the same way in powershell and WSL ubuntu . # Actual behavior In the powershell tab, the ligatures of <= and >= do not work, the rest does. ![image](https://user-images.githubusercontent.com/3267561/60011640-1f796b80-9672-11e9-9d9b-30b2e9f6a3d5.png) In the WSL Ubuntu tab, all the ligatures work ![image](https://user-images.githubusercontent.com/3267561/60011661-31f3a500-9672-11e9-862e-bce795d97464.png)
claunia added the Resolution-By-DesignNeeds-TriageNeeds-Tag-Fix labels 2026-01-30 22:46:09 +00:00
claunia commented 2026-01-30 22:46:10 +00:00
Author
Owner
Copy Link

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

Ligature runs are split in half when the color changes in the middle, which is what powershell is doing. How would you propose this be fixed? The behavior here seems correct.

@DHowett-MSFT commented on GitHub (Jun 24, 2019): Ligature runs are split in half when the color changes in the middle, which is what powershell is doing. How would you propose this be fixed? The behavior here seems correct.
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 Needs-Tag-Fix Needs-Triage Resolution-By-Design
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#2075
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?