Support win32 input mode in the terminal #135127
Labels
feature-request
Request for new features or functionality
*out-of-scope
Posted issue is not in scope of VS Code
terminal
General terminal issues that don't fall under another label
terminal-conpty
Integrated terminal issues related to the ConPTY backend
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
upstream-issue-linked
This is an upstream issue that has been reported upstream
windows
VS Code on Windows issues
Milestone
Newer versions of Conpty feature a win32 input mode which will cause it to always request this particular when it's support by conpty with:
If the terminal supports it, it can then send full blown native input records encoded as strings, see docs here: https://github.com/microsoft/terminal/blob/main/doc/specs/%234999%20-%20Improved%20keyboard%20handling%20in%20Conpty.md
This would enable a whole bunch of keybindings that work in the older Windows terminals to work, for example:
Upstream issue: xtermjs/xterm.js#2357
The text was updated successfully, but these errors were encountered: