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

Not able to maintain scroll position if terminal is outputting new data, have to fight the scroll bar #4205

Closed
vallamost opened this issue Jan 14, 2020 · 2 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@vallamost
Copy link

vallamost commented Jan 14, 2020

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Microsoft Windows [Version 10.0.18362.535]  

Windows Terminal version (if applicable):
Windows Terminal (Preview)
Version: 0.7.3451.0

Any other software?

Apologies if this has been reported already..

Steps to reproduce

Throw this in a bash terminal and run it on the Microsoft Terminal, it's just a simple counter loop:

 my_count=0
 while [  $my_count -lt 1000 ]; do
     echo The count is $my_count
     let my_count=my_count+1
     sleep 0.1
 done

Now try and scroll up and the scroll location will keep changing as more output is received. The terminal should lock is position and ignore the additional output so the operator can focus on the output they are viewing instead you have to fight to maintain your position.

Expected behavior

As the Windows Terminal outputs more information, your scroll position should remain unchanged, you shouldn't have to fight to stay where you are.

Actual behavior

The Windows Terminal will shift your view for each new line of output, the faster the output the harder it is to stay in one position

@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 Jan 14, 2020
@j4james
Copy link
Collaborator

j4james commented Jan 14, 2020

This sounds like a duplicate of #3863.

@vallamost
Copy link
Author

Yep, it is! Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants