You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reading about inverted-wslbridge.exe at mintty/wsltty#41 (comment) ,
I request why the winpty tool can't implement WSL PTY support (aka "WSL winpty adapter").
I like to use the WSL shell as my regular terminal in Windows, for both Windows and WSL Linux command tools. At time, using the wslbridge I can open the WSL shell in any Terminal (CMD, Cygterm, SSHd, etc.). However, I can't execute the winpty from it for the known error of stdin is not a tty. So the only solution to run standard interactive console Windows tools from the WSL shell is, as I see it, to implement the WSL PTY support in winpty.
Please, can you consider this enhancement?
Thank you!
In principle, I think you could ssh from WSL into a Cygwin SSHD, then run winpty.exe from there.
It looks like Microsoft is improving their console/pty/terminal subsystem, and hopefully in the future, the winpty and wslbridge projects won't be needed anymore. See microsoft/terminal#57. It looks like the cmd.exe shell can run inside a WSL Gnome Terminal.
I request why the winpty tool can't implement WSL PTY support (aka "WSL winpty adapter").
I probably could, but I'm not that motivated to work on this.
Hi @rprichard ,
After reading about
inverted-wslbridge.exe
at mintty/wsltty#41 (comment) ,I request why the
winpty
tool can't implement WSL PTY support (aka "WSL winpty adapter").I like to use the WSL shell as my regular terminal in Windows, for both Windows and WSL Linux command tools. At time, using the
wslbridge
I can open the WSL shell in any Terminal (CMD, Cygterm, SSHd, etc.). However, I can't execute thewinpty
from it for the known error ofstdin is not a tty
. So the only solution to run standard interactive console Windows tools from the WSL shell is, as I see it, to implement the WSL PTY support inwinpty
.Please, can you consider this enhancement?
Thank you!
Note: Regarding the idea of accessing to Win32 name pipes from WSL, the project
npiperelay
does it (using go):https://github.com/jstarks/npiperelay
https://github.com/tprasadtp/npiperelay
The text was updated successfully, but these errors were encountered: