-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Terminal input not working with ConPTY disabled #3397
Comments
See if enabling ConPTY under Settings -> Shell helps |
Same here. Windows 2016 Server (roughly the same as Windows 10 1607), no ConPTY support |
Bump up, I got same error. and no conpty support |
Yes, exactly. No ConPTY property under settings->shell. I also have to add that I tried:
It's such a nice and promising terminal app, that I would really appreciate if that one is fixed and I could finally use it :) |
Thanks. Enabling ConPTY works. |
Upstream issue: microsoft/node-pty#457 |
Changed release from 1.0.130 --> 1.0.132Nothing has changed regarding keyboard input on Windows 7:
Any plans fixing it in the nearest future? :) |
Windows Server 2016, no ConPTY version. In addition to the socket error, I'm seeing this:
Hope that helps! P.S. Thank you for this wonderful program! I started to love command line after I started using it! |
Version: 1.0.130
Platform: win32 6.1.7601
Plugins: none
Whenever key is pressed in the terminal, app is throwing following exception:
events.js:292 Uncaught Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:456) at WindowsTerminal._doWrite (C:\Users\xxx\AppData\Local\Programs\Terminus\resources\app.asar\node_modules\@terminus-term\node-pty\lib\windowsTerminal.js:114) at WindowsTerminal._defer (C:\Users\xxx\AppData\Local\Programs\Terminus\resources\app.asar\node_modules\@terminus-term\node-pty\lib\windowsTerminal.js:156) at WindowsTerminal._write (C:\Users\xxx\AppData\Local\Programs\Terminus\resources\app.asar\node_modules\@terminus-term\node-pty\lib\windowsTerminal.js:111) at WindowsTerminal.Terminal.write (C:\Users\xxx\AppData\Local\Programs\Terminus\resources\app.asar\node_modules\@terminus-term\node-pty\lib\terminal.js:81) at Session.write (C:\Users\xxx\AppData\Local\Programs\Terminus\resources\builtin-plugins\terminus-terminal\dist\index.js:12988) at TerminalTabComponent.sendInput (C:\Users\xxx\AppData\Local\Programs\Terminus\resources\builtin-plugins\terminus-terminal\dist\index.js:8736) at SafeSubscriber._next (C:\Users\xxx\AppData\Local\Programs\Terminus\resources\builtin-plugins\terminus-terminal\dist\index.js:8964) at SafeSubscriber.__tryOrUnsub (C:\Users\xxx\AppData\Local\Programs\Terminus\resources\app.asar\node_modules\rxjs\internal\Subscriber.js:205) at SafeSubscriber.next (C:\Users\xxx\AppData\Local\Programs\Terminus\resources\app.asar\node_modules\rxjs\internal\Subscriber.js:143)
Full_Debug.log
The text was updated successfully, but these errors were encountered: