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

Disable the … ligature in Terminal. #7577

New Issue
Closed
opened 2026-01-31 01:07:44 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 01:07:44 +00:00
Owner
Copy Link

Originally created by @PetterS on GitHub (Apr 23, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.778]  
Windows Terminal version (if applicable): 0.11.1121.0

Steps to reproduce

Type "." repeatedly in WSL

Actual behavior

A ligature (…) appears when the number of periods is three.

This is not desired because a lot of software prints progress by repeatedly printing "." and this ligature is aesthetically not very pleasing.

Originally created by @PetterS on GitHub (Apr 23, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- 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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. 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.18363.778] Windows Terminal version (if applicable): 0.11.1121.0 ``` # Steps to reproduce Type "." repeatedly in WSL # Actual behavior A ligature (…) appears when the number of periods is three. This is not desired because a lot of software prints progress by repeatedly printing "." and this ligature is aesthetically not very pleasing.
claunia added the Resolution-Duplicate label 2026-01-31 01:07:44 +00:00
claunia commented 2026-01-31 01:07:44 +00:00
Author
Owner
Copy Link

@PetterS commented on GitHub (Apr 23, 2020):

A setting to completely disable ligatures would solve the problem.

Even though I think having a "…" ligature make very little sense for fixed-width fonts where we still have to make sure the horizontal space is equal to three "."

@PetterS commented on GitHub (Apr 23, 2020): A setting to completely disable ligatures would solve the problem. Even though I think having a "…" ligature make very little sense for fixed-width fonts where we still have to make sure the horizontal space is equal to three "."
claunia commented 2026-01-31 01:07:44 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (Apr 23, 2020):

The ligature in the font could be altered to only switch to the proper ellipsis after there are three full stops, followed by a space.

@mdtauk commented on GitHub (Apr 23, 2020): The ligature in the font could be altered to only switch to the proper ellipsis after there are three full stops, followed by a space.
claunia commented 2026-01-31 01:07:45 +00:00
Author
Owner
Copy Link

@PetterS commented on GitHub (Apr 23, 2020):

The ligature in the font could be altered to only switch to the proper ellipsis after there are three full stops, followed by a space.

Yes, that would fix most of the problem. I see no point of having it at all though.

@PetterS commented on GitHub (Apr 23, 2020): > The ligature in the font could be altered to only switch to the proper ellipsis after there are three full stops, followed by a space. Yes, that would fix most of the problem. I see no point of having it at all though.
claunia commented 2026-01-31 01:07:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 23, 2020):

this ligature is aesthetically not very pleasing.

That's really a "eye of the beholder" kind of thing though, isn't it? You're always free to chose another font that doesn't have that ligature if you want.

Broadly, settings to disable ligatures are being tracked in /dup #759, so we can continue the discussion over in that thread. Thanks!

@zadjii-msft commented on GitHub (Apr 23, 2020): > this ligature is aesthetically not very pleasing. That's really a "eye of the beholder" kind of thing though, isn't it? You're always free to chose another font that _doesn't_ have that ligature if you want. Broadly, settings to disable ligatures are being tracked in /dup #759, so we can continue the discussion over in that thread. Thanks!
claunia commented 2026-01-31 01:07:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 23, 2020):

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 (Apr 23, 2020): 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 01:07:45 +00:00
Author
Owner
Copy Link

@PetterS commented on GitHub (Apr 23, 2020):

That's really a "eye of the beholder" kind of thing though, isn't it?

@zadjii-msft

Sure, by itself it may be. But when it is part of an animation of "." being printed one at a time, it is a clear visual bug.

May not be high priority, but I think this is a bug either in Terminal or maybe in Cascadia Code which seems to be installed by Terminal.

@PetterS commented on GitHub (Apr 23, 2020): > That's really a "eye of the beholder" kind of thing though, isn't it? @zadjii-msft Sure, by itself it may be. But when it is part of an animation of "." being printed one at a time, it is a clear visual bug. May not be high priority, but I think this is a bug either in Terminal or *maybe* in Cascadia Code which seems to be installed by Terminal.
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 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#7577
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?