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

Cursor droppings on wide chars in Windows Terminal #19194

New Issue
Closed
opened 2026-01-31 06:36:28 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 06:36:28 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Jan 10, 2023).

Windows Terminal version

1.16.2641.0

Windows build number

10.0.19044.2364

Other Software

No response

Steps to reproduce

  1. Open a WSL bash shell in Windows Terminal.
  2. Execute printf "\e[2 q\e[2J\e[1;999H\e[D\u306F"; sleep 1; printf "\e[B\n"

This sequence is performing the following steps:

  1. The cursor style is set to a non-blinking block (just to make the bug more obvious).
  2. The screen is cleared, and the cursor moved to the top right corner.
  3. The cursor is then moved one column back and a wide character (は) is written out.
  4. We wait for a second, to give the cursor a chance to render.
  5. The cursor is moved down a line.
  6. We output a newline (just so the shell prompt is back at the start of the line).

Expected Behavior

At the end of all that, there should only be one cursor visible on the screen.

Actual Behavior

In addition to the real cursor at the shell prompt, there is a second cursor left behind overlapping the は character.

image

I realise this is probably not a typical scenario that you're likely to encounter, but it'll become more common once Windows Terminal implements delayed EOL wrap correctly (which is one of the thing I'm hoping to fix in PR #14640).

Originally created by @j4james on GitHub (Jan 10, 2023). ### Windows Terminal version 1.16.2641.0 ### Windows build number 10.0.19044.2364 ### Other Software _No response_ ### Steps to reproduce 1. Open a WSL bash shell in Windows Terminal. 2. Execute `printf "\e[2 q\e[2J\e[1;999H\e[D\u306F"; sleep 1; printf "\e[B\n"` This sequence is performing the following steps: 1. The cursor style is set to a non-blinking block (just to make the bug more obvious). 2. The screen is cleared, and the cursor moved to the top right corner. 3. The cursor is then moved one column back and a wide character (`は`) is written out. 5. We wait for a second, to give the cursor a chance to render. 6. The cursor is moved down a line. 7. We output a newline (just so the shell prompt is back at the start of the line). ### Expected Behavior At the end of all that, there should only be one cursor visible on the screen. ### Actual Behavior In addition to the real cursor at the shell prompt, there is a second cursor left behind overlapping the `は` character. ![image](https://user-images.githubusercontent.com/4181424/211568625-b393f0a2-7efb-4b0a-9e9b-5373563a7e7c.png) I realise this is probably not a typical scenario that you're likely to encounter, but it'll become more common once Windows Terminal implements delayed EOL wrap correctly (which is one of the thing I'm hoping to fix in PR #14640).
claunia added the Needs-TriageResolution-Fix-CommittedIssue-Bug labels 2026-01-31 06:36:28 +00:00
claunia commented 2026-01-31 06:36:29 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jan 10, 2023):

Note that this is not the same thing as #12739, which was the result of deferred cursor drawing. This is the result of a miscalculation in the cursor bounds checking, as explained in https://github.com/microsoft/terminal/pull/13001#discussion_r862125419.

@j4james commented on GitHub (Jan 10, 2023): Note that this is not the same thing as #12739, which was the result of deferred cursor drawing. This is the result of a miscalculation in the cursor bounds checking, as explained in https://github.com/microsoft/terminal/pull/13001#discussion_r862125419.
claunia commented 2026-01-31 06:36:29 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 24, 2023):

:tada:This issue was addressed in #14661, which has now been successfully released as Windows Terminal Preview v1.17.1023.🎉

Handy links:

@ghost commented on GitHub (Jan 24, 2023): :tada:This issue was addressed in #14661, which has now been successfully released as `Windows Terminal Preview v1.17.1023`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.17.1023) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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 Resolution-Fix-Committed
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#19194
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?