Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cursor droppings in WT cmd shell #17615

Closed
j4james opened this issue Jul 25, 2024 · 2 comments · Fixed by #17617
Closed

Cursor droppings in WT cmd shell #17615

j4james opened this issue Jul 25, 2024 · 2 comments · Fixed by #17617
Labels
Area-Rendering Text rendering, emoji, complex glyph & font-fallback issues In-PR This issue has a related PR Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Priority-3 A description (P3) Product-Conhost For issues in the Console codebase

Comments

@j4james
Copy link
Collaborator

j4james commented Jul 25, 2024

Windows Terminal version

Commmit 75f7ae4

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.

@j4james j4james added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 25, 2024
@j4james
Copy link
Collaborator Author

j4james commented Jul 25, 2024

It looks like commit 0a2b660 is the cause.

@lhecker lhecker added Product-Conhost For issues in the Console codebase Area-Rendering Text rendering, emoji, complex glyph & font-fallback issues Priority-3 A description (P3) and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 25, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Tag-Fix Doesn't match tag requirements label Jul 26, 2024
@DHowett
Copy link
Member

DHowett commented Jul 26, 2024

Thanks for bisecting, James!

@microsoft-github-policy-service microsoft-github-policy-service bot added the In-PR This issue has a related PR label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Rendering Text rendering, emoji, complex glyph & font-fallback issues In-PR This issue has a related PR Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Priority-3 A description (P3) Product-Conhost For issues in the Console codebase
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants