terminal: Scrolling within regions that include the top of the screen doesn't push lines into scrollback
Environment
Windows Terminal version: Version: 0.6.2951.0 Microsoft Windows [Version 10.0.18362.418]
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):
Any other software?
Steps to reproduce
- Install Ubuntu 18.04 (on WSL 1.0), install minicom inside Ubuntu.
- Open Windows Terminal and run Ubuntu 18.04
- Open minicom from Windows Terminal and try to capture serial console message from any embedded dev. board (say Raspberry PI)
- You will see messages scrolling above the view port. If you scroll up you won’t see the messages from the minicom.
Expected behavior
If I scroll up, I should be able to see the serial console messages from my embedded target.
Actual behavior
Scroll up shows my command that I typed long ago. The serial console message is lost. If I run Ubuntu terminal directly (instead of doing the same from Windows Terminal), I could scroll up and see right messages.
Not sure, may be ncurses behavior is not compatible with Windows Terminal’s expectations?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 10
- Comments: 20 (10 by maintainers)
FYI, I think I may have inadvertently fixed this issue while I was working on merging the
LineFeed
implementations intoAdaptDispatch
for issue #13408. It will probably be a while still before I have PR ready for that, and I’m not positive it’ll fix this issue completely, but it looks promising so far.Hi, is there any plan to fix this issue soon?
Just writing to say I found this post googling the same issue.
In Windows terminal, SSH’d into a rPi, running minicom results in not being able to see previous output from minicom. If you scroll up it shows the bash command before minicom launched, but not the output from minicom.
In Visual Studio Code Terminal, SSH’d into the same rPi, running minicom results in being able to scroll up and down like normal, and see the full history of minicom.
In a vanilla windows command prompt (as well as powershell), SSH/rPi/minicom works as expected (you can mousewheel up to see previous minicom output).
It’s only in Windows Terminal where it’s all screwy and annoying. 😦
Thanks for the hard work though guys! I’m a big fan of terminal!
I’m re-opening this to track the scrolling margins + conpty issue, and tossing it on the backlog. Thanks!