ConPTY Passthrough mode #1985
Labels
Area-Server
Down in the muck of API call servicing, interprocess communication, eventing, etc.
Issue-Feature
Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
Product-Conpty
For console issues specifically related to conpty
Resolution-Duplicate
There's another issue on the tracker that's pretty much the same thing.
I've discussed this a couple times on different threads before, but I think I never made a real issue for it.
The idea of conpty passthrough mode is that a commandline client application that knows it's only going to use VT sequences (and not the API) to modify the console could set a special mode,
ENABLE_PASSTHROUGH_MODE
. If conpty is active, the console would then stop rendering itself over conpty, and anything that was written to the console would go straight to the terminal.wsl
, where it's only ever going to be talking VT.This has some rough edges that need to be sorted out.
Get/SetConsoleMode
and reading input / writing output.This needs a real spec written, but it probably needs prototyping done before that.
The text was updated successfully, but these errors were encountered: