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
Errors no longer caught #37
Comments
The node-pty guys have no intention of fixing this. Should we remove the |
What do you mean by "this"? Can you give a link with your statement?
El 29/07/2017 04:58, "Steven Vachon" <notifications@github.com> escribió:
… The node-pty guys have no intention of fixing this. Should we remove the
error event, then, or is there a need to emit stream errors?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgfviN2tp5L7RKNTgKKii1GaHL2vGcsks5sSp_bgaJpZM4OXmNR>
.
|
There is a link in the original comment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before, I would
console.error(error); process.exitCode = 1
and the "error" event would be emitted. This is no longer happening now that I'm not using v0.6.2 from npmmicrosoft/node-pty#71
The text was updated successfully, but these errors were encountered: