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 position is lost when resizing the window horizontally #10868

Closed
daanx opened this issue Aug 4, 2021 · 6 comments
Closed

Cursor position is lost when resizing the window horizontally #10868

daanx opened this issue Aug 4, 2021 · 6 comments
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. Priority-2 A description (P2) Product-Terminal The new Windows Terminal.

Comments

@daanx
Copy link

daanx commented Aug 4, 2021

Windows Terminal version (or Windows build number)

10.0.19042.1110 (windows terminal 1.9.1942.0)

Other Software

No response

Steps to reproduce

When the windows is horizontally resized the cursor position is lost; on the narrowing the cursor wraps to the next line, but on widening again the cursor goes incorrectly to the start of the previous line.
(Extra heisenbug: if you quickly resize narrow again the cursor will go randomly in the text :-)

To reproduce run the following batch file:

@echo off
set /p "ANSWER=prompt prompt prompt prompt prompt prompt prompt>"

Expected Behavior

On the old cmd terminal the batch file works as intended.

Actual Behavior

Here is what happens in Windows terminal (I colored the cursor in red):

cursor-bug

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Aug 4, 2021
@daanx
Copy link
Author

daanx commented Aug 4, 2021

perhaps this is related to the earlier bug I filed #10848 ?

@zadjii-msft
Copy link
Member

This probably is closely related, maybe even the same root cause, but I like having lots of test cases, and these are great repro steps. Thanks!

@zadjii-msft zadjii-msft added Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-2 A description (P2) Product-Terminal The new Windows Terminal. labels Aug 4, 2021
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 4, 2021
@zadjii-msft zadjii-msft added this to the Terminal v2.0 milestone Aug 4, 2021
@zadjii-msft zadjii-msft removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Aug 5, 2021
@zadjii-msft zadjii-msft modified the milestones: Terminal v2.0, 22H2 Jan 4, 2022
@zadjii-msft zadjii-msft modified the milestones: 22H2, Backlog Jul 5, 2023
@lhecker
Copy link
Member

lhecker commented Aug 15, 2023

I'm trying to reproduce this bug to test if #15701 fixed it but couldn't do manage to reproduce it. Does this bug still happen in 1.17/1.18?

@lhecker lhecker added the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Aug 15, 2023
@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Aug 15, 2023
@zadjii-msft zadjii-msft modified the milestones: Backlog, Terminal v1.19 Aug 15, 2023
@lhecker
Copy link
Member

lhecker commented Aug 15, 2023

BTW I think we should close this issue in favor of #10848. From what I can tell they're the same issue if anything. Also, I managed to reproduce something although not using the given instructions. I'll comment in #10848.

@microsoft-github-policy-service
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

1 similar comment
@microsoft-github-policy-service
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Aug 19, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot removed this from the Terminal v1.19 milestone Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. Priority-2 A description (P2) Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

3 participants