Currently pty.js drives communication to and from the terminal's shell process but there are some issues with the way it's setup:
Hi @Tyriar , thanks for your work on this! Just FYI I also tried ptyw.js but with no luck. Finally I had to fallback to use cmd.exe to get result of a command. Looking forward to a stable pty.js! 👏
The winpty version used in Tyriar/pty.js is a little newer than peters/winpty.
It's from jeremyramin/winpty@a988fe99934c59e5f518f6f90a60f52c72ee3f31
@the-ress thanks for pointing that out, I wasn't aware :smiley:
I've enabled issues on Tyriar/pty.js so I can better organize the issues.
I replaced the master branch with the prebuilt branch and set the default back to master. It's fine to point at master now.
Here's the plan:
0.3.1 itself is unstable due to https://github.com/rprichard/winpty/issues/80
Mr @Tyriar You should ask WDG to include an OFFICIAL PTY API into Creaters’ update.
cf. Microsoft/BashOnWindows#1117
@be5invis while that would be nice, it won't fix the problem from my end (for a long time) as we will need to support legacy Windows. 👍'd though.
An update on this: I've currently put the upgrade on hold as my initial testing of winpty 0.4.1 shows some breakages such as git bash moving the cursor in the wrong direction after backspace and many glitches in Bash for Windows. This is still a stretch goal for this iteration so I'm going to focus on finishing up the other stuff I have assigned this iteration before looking further into this.
I have however published the lib with all the fixes from before (what we ship in stable) as [email protected] npm so other consumers are safe to use that npm package if they were previously pointing to c75c2dc on Tyriar/pty.js. The only change was in the package.json metadata.
I filed https://github.com/rprichard/winpty/issues/96 on the winpty repo outlining the major issues I see
One of the issues was node-pty's fault which has been fixed, the one last issue I believe has already been fixed (https://github.com/rprichard/winpty/commit/40d5b72c43165875724825fab5b5e5303fa5c3c3) and is just waiting for the new winpty version! :tada:
I just pushed to master to use [email protected] which includes the winpty fix for applications within WSL. If all goes well I'll release the new version of node-pty.
Most helpful comment
Here's the plan:
0.4.00.4.1 https://github.com/Tyriar/pty.js/issues/10