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

Resizing the window should keep the prompt at the bottom of the window #17033

Open
warpdesign opened this issue Apr 9, 2024 · 2 comments
Open
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Conpty For console issues specifically related to conpty
Milestone

Comments

@warpdesign
Copy link

warpdesign commented Apr 9, 2024

Windows Terminal version

1.19.105.73.0

Windows build number

10.0.19045.4239

Other Software

No response

Steps to reproduce

  • open a Windows Terminal
  • fill the buffer so that the prompt appears at the bottom of the window
  • resize the window so that it's smaller than before
  • enlarge the window

Expected Behavior

The prompt should stay at the bottom of the window.

Actual Behavior

The prompt has moved several lines up (scroll position appears to be correct: at the bottom of the window, but the text/prompt's position is not correct). Also notice one of the previous prompt that incorrectly appears on the top right, but I guess it should go in another issue.

WindowsTerminal_WpzsHj6hwD.mp4

The expected behavior is the one I saw on popular terminal apps on macOS and Linux.

For example:

iTerm on mac

Screen.Recording.2024-04-09.at.16.18.01.mov

GNOME Terminal on Debian

Screen.Recording.2024-04-09.at.16.15.21.mov
@warpdesign warpdesign 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 Apr 9, 2024
Copy link

github-actions bot commented Apr 9, 2024

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@carlos-zamora carlos-zamora removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Apr 10, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Tag-Fix Doesn't match tag requirements label Apr 10, 2024
@carlos-zamora
Copy link
Member

Thanks for filing. We do this for consistency with the Windows Console. We have an idea of how to approach this, but it's actually a pretty big architectural change. This should definitely be linked up to #15065 though, since ConPTY is involved

@carlos-zamora carlos-zamora added Product-Conpty For console issues specifically related to conpty Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. and removed Needs-Tag-Fix Doesn't match tag requirements Issue-Bug It either shouldn't be doing this or needs an investigation. labels Apr 10, 2024
@carlos-zamora carlos-zamora added this to the Backlog milestone Apr 10, 2024
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-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Conpty For console issues specifically related to conpty
Projects
None yet
Development

No branches or pull requests

2 participants