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

Bug Report - Font Ligatures interact with the shell prompt #1255

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

Originally created by @tensor-programming on GitHub (May 22, 2019).

Environment

Windows 1903
Fira Code with Font Ligatures enabled

Steps to reproduce

Use a font with font ligatures and type - or = as your first character.

Expected behavior

I would expect the prompt not to interact with the characters. In c:\projects\> the > symbol should not connect with any font ligatures.

Actual behavior

The > symbol combines to create font ligatures.

The behavior is shown in the below images:
font-ligatures-error-1
font-ligatures-error-2

Originally created by @tensor-programming on GitHub (May 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 Windows 1903 Fira Code with Font Ligatures enabled # Steps to reproduce Use a font with font ligatures and type `-` or `=` as your first character. # Expected behavior I would expect the prompt not to interact with the characters. In `c:\projects\>` the `>` symbol should not connect with any font ligatures. # Actual behavior The `>` symbol combines to create font ligatures. The behavior is shown in the below images: ![font-ligatures-error-1](https://user-images.githubusercontent.com/22513880/58168814-2a00a980-7c5d-11e9-9715-8450d8f7d3ba.png) ![font-ligatures-error-2](https://user-images.githubusercontent.com/22513880/58168822-2cfb9a00-7c5d-11e9-8d83-0d617506bb57.png)
claunia added the Area-RenderingIssue-BugResolution-DuplicateProduct-Terminal labels 2026-01-30 22:20:19 +00:00
claunia commented 2026-01-30 22:20:20 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (May 22, 2019):

The Prompt should really be self contained. Maybe the settings screen should provide a visual way to choose your own prompt, if you wanted to use CharacterMap to insert a character, or a ligature sequence that wont combine with characters after it.

@mdtauk commented on GitHub (May 22, 2019): The Prompt should really be self contained. Maybe the settings screen should provide a visual way to choose your own prompt, if you wanted to use CharacterMap to insert a character, or a ligature sequence that wont combine with characters after it.
claunia commented 2026-01-30 22:20:20 +00:00
Author
Owner
Copy Link

@tensor-programming commented on GitHub (May 22, 2019):

Yes, this is what I am thinking as well. Decoupling the prompt from the inputted text to allow for different options. Then maybe custom prompts would also be possible.

In WSL at least there is a space between the prompt and the input so Ligatures are not possible. However, in both powershell and cmd it seems that they are.

@tensor-programming commented on GitHub (May 22, 2019): Yes, this is what I am thinking as well. Decoupling the prompt from the inputted text to allow for different options. Then maybe custom prompts would also be possible. In WSL at least there is a space between the prompt and the input so Ligatures are not possible. However, in both powershell and cmd it seems that they are.
claunia commented 2026-01-30 22:20:20 +00:00
Author
Owner
Copy Link

@HBelusca commented on GitHub (May 22, 2019):

Would inserting an (invisible) zero-width unicode space character after the end of the prompt fix the problem?

@HBelusca commented on GitHub (May 22, 2019): Would inserting an (invisible) zero-width unicode space character after the end of the prompt fix the problem?
claunia commented 2026-01-30 22:20:21 +00:00
Author
Owner
Copy Link

@tensor-programming commented on GitHub (May 22, 2019):

You could fix the problem with a break character of any kind. Ligatures are combinations of unicode characters to build symbols and they are a part of the font.

@tensor-programming commented on GitHub (May 22, 2019): You could fix the problem with a break character of any kind. Ligatures are combinations of unicode characters to build symbols and they are a part of the font.
claunia commented 2026-01-30 22:20:21 +00:00
Author
Owner
Copy Link

@glen-84 commented on GitHub (May 22, 2019):

Duplicate of #514.

@glen-84 commented on GitHub (May 22, 2019): Duplicate of #514.
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#1255
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?