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

Incorrect cursor positioning for certain unicode special characters #22436

New Issue
Closed
opened 2026-01-31 08:13:10 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:13:10 +00:00
Owner
Copy Link

Originally created by @jjcarrier on GitHub (Oct 20, 2024).

Windows Terminal version

1.21.2701.0

Windows build number

10.0.22631.0

Other Software

Also tested on Windows Terminal v1.22.2702.0

Steps to reproduce

  1. Paste the following into the terminal
'✅' | Format-Hex

Observe cursor position, then press enter.

  1. Paste the following into the terminal
'👨‍👩‍👧‍👦' | Format-Hex

Expected Behavior

  1. The cursor position should be immediately following the x character.
  2. The cursor position should be immediately following the x character.

Actual Behavior

  1. The cursor position is off by one and you cannot move the cursor past the x character.
  2. The cursor position is many characters past where it should be.
Originally created by @jjcarrier on GitHub (Oct 20, 2024). ### Windows Terminal version 1.21.2701.0 ### Windows build number 10.0.22631.0 ### Other Software Also tested on Windows Terminal v1.22.2702.0 ### Steps to reproduce 1. Paste the following into the terminal ```pwsh '✅' | Format-Hex ``` Observe cursor position, then press enter. 2. Paste the following into the terminal ```pwsh '👨‍👩‍👧‍👦' | Format-Hex ``` ### Expected Behavior 1. The cursor position should be immediately following the `x` character. 2. The cursor position should be immediately following the `x` character. ### Actual Behavior 1. The cursor position is off by one and you cannot move the cursor past the `x` character. 2. The cursor position is many characters past where it should be.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:13:11 +00:00
claunia commented 2026-01-31 08:13:12 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 20, 2024):

Which shell are you using? Do you know whether it supports grapheme clusters?

The shell is unfortunately involved in cursor positioning. If it has an incongruous understanding of the layout of the screen from the terminal it is hosted in, it will tell Terminal the wrong cursor position.

@DHowett commented on GitHub (Oct 20, 2024): Which shell are you using? Do you know whether it supports grapheme clusters? The shell is unfortunately involved in cursor positioning. If it has an incongruous understanding of the layout of the screen from the terminal it is hosted in, it will tell Terminal the wrong cursor position.
claunia commented 2026-01-31 08:13:12 +00:00
Author
Owner
Copy Link

@jjcarrier commented on GitHub (Oct 20, 2024):

@DHowett I tried this on both PowerShell v7.4.5 and preview v7.5.0.

NOTE: I fixed incorrect instructions above that omitted the quotes, in case that caused confusion.

And regarding grapheme clusters, I am not familiar with this (a quick search suggests PowerShell does not have built-in support for this?), but I think this points to a solution for solving the issue I have with a custom pager. So, thank you for mentioning this.

@jjcarrier commented on GitHub (Oct 20, 2024): @DHowett I tried this on both PowerShell v7.4.5 and preview v7.5.0. NOTE: I fixed incorrect instructions above that omitted the quotes, in case that caused confusion. And regarding grapheme clusters, I am not familiar with this (a quick search suggests PowerShell does not have built-in support for this?), but I think this points to a solution for solving the issue I have with a custom pager. So, thank you for mentioning this.
claunia commented 2026-01-31 08:13:12 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 21, 2024):

PowerShell indeed does not yet have support for complex graphemes and so it misplaces the cursor. That's not something we can fix on our side, unfortunately.

@lhecker commented on GitHub (Oct 21, 2024): PowerShell indeed does not yet have support for complex graphemes and so it misplaces the cursor. That's not something we can fix on our side, unfortunately.
claunia commented 2026-01-31 08:13:12 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 21, 2024):

I'll be closing the issue for now. Let us know if you find any issues with our implementation when used with a shell/application that supports them. You can try cmd.exe, for instance.

@lhecker commented on GitHub (Oct 21, 2024): I'll be closing the issue for now. Let us know if you find any issues with our implementation when used with a shell/application that supports them. You can try cmd.exe, for instance.
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 Issue-Bug Needs-Triage
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#22436
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?