-
Notifications
You must be signed in to change notification settings - Fork 251
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
Uplevel winpty to 0.4.1 #10
Comments
Good luck! Let me know if you need any help. |
Is it goint to be released soon? |
Potentially as part of vscode 1.9, I was blocked on this due to bug in 0.4.0 that was fixed in master but not released, it got released after I reached out to the author a couple of days ago https://github.com/rprichard/winpty/releases It is a stretch goal though as the other issues I'm working on are higher priority microsoft/vscode#17608 |
Success! #20 |
Running into some issues introduced by [email protected] which seem to make some things worse. FWIW bash on windows seems really solid, provided it's running |
I actually has many troubles now with vscode terminal (with bash, and I think cmd behaves the same way): after multiple commands the whole command line input becomes corrupted - different symbols appear and disappear when try to edit the command) and especially with |
Yeah, unfortunately there seem to be even more issues when running on [email protected] unless I'm missing something; things such as:
Bash on windows with tmux on [email protected] seems really good for some reason though. |
This release seems to have fixed the arrow key in WSL issue microsoft/vscode#10163.
The text was updated successfully, but these errors were encountered: