-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
perform console initialization in windows #2020
Comments
Do try to do things the VT way as much as possible. Some of those things like |
I'd honestly take whatever you need from PDCurses. You could probably use much of what's there to even provide the ncurses shim you've file an issue for. |
i think that failure to enter cbreakesque mode is our main blocker now on Windows Terminal, as we hang up after sending queries, but progress if the user hits enter on the keyboard. |
You should be able to simulate pressing that enter key. Typically simulating user actions are for tests but if that's what's needed until another method can be found, it's a quick work-around. |
alright, we're now advancing forward to creation of the initial plane, which breaks because we don't have good geometry on windows yet |
closing this, and we'll pursue remaining windows issues in their own bugs |
Elements of this are alluded to in #2014. There are a few termios-like functions we need to call in Windows during initialization.
SetConsoleMode()
https://docs.microsoft.com/en-us/windows/console/setconsolemodeENABLE_PROCESSED_OUTPUT
,ENABLE_VIRTUAL_TERMINAL_PROCESSING
,ENABLE_WINDOW_INPUT
,ENABLE_MOUSE_INPUT
all look relevantGetConsoleScreenBufferInfo()
for screen geometryit looks like we can disable line discipline events with
ENABLE_PROCESSED_INPUT
, enter cbreak mode withENABLE_LINE_INPUT
, and disable echo (see #2019) withENABLE_ECHO_INPUT
The text was updated successfully, but these errors were encountered: