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

Some glyphs are not rendered correctly on a PowerShell prompt #2756

New Issue
Closed
opened 2026-01-30 23:04:17 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:04:17 +00:00
Owner
Copy Link

Originally created by @Tragetaschen on GitHub (Jul 13, 2019).

Environment

Windows build number: 10.0.18932.1000, but I'm seeing at least since 17763
Windows Terminal version (if applicable): 0.2.1831.0

Steps to reproduce

Open a PowerShell and type 123¹²³ on the prompt (or paste it)

Expected behavior

It should show up as 123¹²³

Actual behavior

It is rendered as if had typed 1231²3, but only on the promt, not in error messages

image

Originally created by @Tragetaschen on GitHub (Jul 13, 2019). # Environment ```none Windows build number: 10.0.18932.1000, but I'm seeing at least since 17763 Windows Terminal version (if applicable): 0.2.1831.0 ``` # Steps to reproduce Open a PowerShell and type `123¹²³` on the prompt (or paste it) # Expected behavior It should show up as `123¹²³` # Actual behavior It is rendered as if had typed `1231²3`, but only on the promt, not in error messages ![image](https://user-images.githubusercontent.com/1947968/61175209-a784ce00-a5ab-11e9-84cc-a1b7991df18a.png)
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-30 23:04:17 +00:00
claunia commented 2026-01-30 23:04:18 +00:00
Author
Owner
Copy Link

@sunyinqi0508 commented on GitHub (Jul 14, 2019):

This seems like a bug from PowerShell that substitutes ¹ with 1 rather than wt.

@sunyinqi0508 commented on GitHub (Jul 14, 2019): This seems like a bug from PowerShell that substitutes ¹ with 1 rather than wt.
claunia commented 2026-01-30 23:04:18 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 14, 2019):

Good guess! Just checked the powershell parser, though. These are the only special characters it treats differently.

Incidentally, though, you mentioned that you've been seeing it since 17763 -- so it's definitely not going to be a Windows Terminal issue. I can't even paste 123¹²³ in through conhost. PSReadline drops the superscripts completely.

If I Remove-Module PSReadline, it suddenly starts working.

It might be worth following up at lzybkr/PSReadline. 17763 is the first version that included PSReadline 2.0.0.

@DHowett-MSFT commented on GitHub (Jul 14, 2019): Good guess! Just checked the powershell parser, though. [These](https://github.com/PowerShell/PowerShell/blob/d6390461b2eeafb8aeb5dcfeff8134c2bca90d86/src/System.Management.Automation/engine/parser/CharTraits.cs#L6-L25) are the only special characters it treats differently. Incidentally, though, you mentioned that you've been seeing it since 17763 -- so it's definitely not going to be a Windows Terminal issue. I can't even paste `123¹²³` in through conhost. PSReadline drops the superscripts completely. If I `Remove-Module PSReadline`, it suddenly starts working. It might be worth following up at [lzybkr/PSReadline](https://github.com/lzybkr/PSReadline). 17763 is the first version that included PSReadline 2.0.0.
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 Resolution-External
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#2756
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?