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

Cursor droppings in WT cmd shell #22013

New Issue
Open
opened 2026-01-31 08:00:53 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:00:53 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Jul 25, 2024).

Windows Terminal version

Commmit 75f7ae4bec

Windows build number

10.0.19045.4651

Other Software

No response

Steps to reproduce

I don't know how many of these steps are strictly required, but this is what reproduces the issue for me quite consistently:

  1. Open a cmd shell in Windows Terminal.
  2. Create a directory with 6 files in it.
  3. Make sure the screen height is 24 rows.
  4. Clear the screen with cls.
  5. Execute dir twice in a row.

Expected Behavior

Only one instance of the cursor should be visible on the screen.

Actual Behavior

There is an extra zombie cursor dropping left after the second dir is typed.

image

It happens quite consistently for me, but not every time, and it disappears quite easily - switching to another window and back again is usually enough. That made it very difficult to screenshot. I had to take a video and save one of the frames.

I can't reproduce it in the preview build (1.21.1272.0), so I'm assuming it's a regression. I'll try and do a git bisect later to see if I can figure out the exact commit.

Originally created by @j4james on GitHub (Jul 25, 2024). ### Windows Terminal version Commmit 75f7ae4bec2f859b3f54043bd5c1a36161885a4d ### Windows build number 10.0.19045.4651 ### Other Software _No response_ ### Steps to reproduce I don't know how many of these steps are strictly required, but this is what reproduces the issue for me quite consistently: 1. Open a cmd shell in Windows Terminal. 2. Create a directory with 6 files in it. 3. Make sure the screen height is 24 rows. 4. Clear the screen with `cls`. 5. Execute `dir` twice in a row. ### Expected Behavior Only one instance of the cursor should be visible on the screen. ### Actual Behavior There is an extra zombie cursor dropping left after the second `dir` is typed. ![image](https://github.com/user-attachments/assets/a79bd285-8896-4e2f-a92e-21024d287625) It happens quite consistently for me, but not _every_ time, and it disappears quite easily - switching to another window and back again is usually enough. That made it very difficult to screenshot. I had to take a video and save one of the frames. I can't reproduce it in the preview build (1.21.1272.0), so I'm assuming it's a regression. I'll try and do a git bisect later to see if I can figure out the exact commit.
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 In-PR Issue-Bug Needs-Tag-Fix Priority-3 Product-Conhost
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#22013
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?