-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
conhost: SetConsoleWindowInfo broken when used in alternate screen buffer #13741
Comments
As an aside, can you explain the behaviour of the scrollbars?
Is all this just conhost only being able to halfway enforce the buffer size == window size rule for alt buffer? |
The limitation of Windows Terminal being ignoring the |
er, wait though, is it? It sounds like you're trying to use |
@zadjii-msft thanks for your feedback. Yes you are right it's more like #5094 and you'll see some comments I posted there. I don't have any issue by resizing the windows and the buffer with the same size with
I only want to get rid the scrollback while my app is running but when I exit I restore the saved original back. What do you mean by using the alt buffer? |
Oh that's like, literally the whole idea of the "alternate screen buffer"! That's the thing that apps like |
Thanks for your attention. That was what I did for the NetDriver that essential use .NET |
Windows Terminal version
No response
Windows build number
10.0.19041.1806
Other Software
conhost.exe 10.0.19041.1566
conhostV1.dll 10.0.19041.21
Visual Studio 2019 version 16.11.18
Steps to reproduce
Use this test program:
Expected Behavior
No response
Actual Behavior
Recording compiled with Visual Studio 2019 version 16.11.18, default console project with Debug/x86 target.
rqUpmv2sfr.mp4
GetConsoleScreenBufferInfo
,SetConsoleWindowInfo
returns 0 with the invalid parameters error code.SetConsoleWindowInfo
returns non-zero indicating success, but the actual window size remains unchanged.I don't know if resizing is ever supposed to work in the alternate screen buffer, but even if it's supposed to fail, the way it fails seems pretty nonsensical to me.
The text was updated successfully, but these errors were encountered: