-
Notifications
You must be signed in to change notification settings - Fork 209
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
Please release a version of pty.js after update nan to 1.8.4 for iojs build #122
Comments
50 tasks
destitutus
pushed a commit
to codio/pty.js
that referenced
this issue
Jul 5, 2016
* add support for .on('exit', function (code, signal) {}) * use an arg instead of arguments[0] * htop command cannot resize with env.LINSE and env.COLUMNS * v0.2.8. fixes chjj#122. * style conventions. * fix build. see chjj#110. * call uv_close to take cb off the event loop. see chjj#110. * more style fixes. * use older v8 api for function casts? * fix after_wait_on_pid for node v0.10.x. see chjj#110. * fix close events. see chjj#110. * v0.2.9 * refactor waitpid thread. * refactor pty.fork args. * free up baton in uv_close callback. see chjj#110. * fix issue where exit is emitted before the last data event. see chjj#110. * account for node v0.8.x on waitpid. see chjj#110. * v0.2.10 * add comment. * v0.2.11 * better onexit callback. * event better onexit callback. see chjj#110. * v0.2.12 * create scope in pty_after_waitpid to prevent fatal v8 error in io.js. fixes chjj#126. * v0.2.13 * upgrade to nan 2.0.5. see chjj#127. * remove "heap-style" Nan::Callback. * strict nan version. * remove useless v8 namespace prefixes. * minor: whitespace. cols. * bind to close only once. * v0.3.0 * update win/pty.cc to work with nan 2.0.5 * Optional resuming of the socket The immediate resumption the a socket means that output can be lost unless you start consuming it right away. In some cases, this behavior is undesirable. Adding an option to not automatically resume the socket enables data to be read after a delay. * Update nan version
ddm
pushed a commit
to ddm/pty.js
that referenced
this issue
Nov 8, 2017
destitutus
added a commit
to codio/pty.js
that referenced
this issue
Jun 21, 2018
* add support for .on('exit', function (code, signal) {}) * use an arg instead of arguments[0] * htop command cannot resize with env.LINSE and env.COLUMNS * v0.2.8. fixes chjj#122. * style conventions. * fix build. see chjj#110. * call uv_close to take cb off the event loop. see chjj#110. * more style fixes. * use older v8 api for function casts? * fix after_wait_on_pid for node v0.10.x. see chjj#110. * fix close events. see chjj#110. * v0.2.9 * refactor waitpid thread. * refactor pty.fork args. * free up baton in uv_close callback. see chjj#110. * fix issue where exit is emitted before the last data event. see chjj#110. * account for node v0.8.x on waitpid. see chjj#110. * v0.2.10 * add comment. * v0.2.11 * better onexit callback. * event better onexit callback. see chjj#110. * v0.2.12 * create scope in pty_after_waitpid to prevent fatal v8 error in io.js. fixes chjj#126. * v0.2.13 * upgrade to nan 2.0.5. see chjj#127. * remove "heap-style" Nan::Callback. * strict nan version. * remove useless v8 namespace prefixes. * minor: whitespace. cols. * bind to close only once. * v0.3.0 * update win/pty.cc to work with nan 2.0.5 * Optional resuming of the socket The immediate resumption the a socket means that output can be lost unless you start consuming it right away. In some cases, this behavior is undesirable. Adding an option to not automatically resume the socket enables data to be read after a delay. * update dependency [email protected] to [email protected] * update nan to @2.3.5 * v0.3.1 * pty.kill is not a function see https://codio.myjetbrains.com/youtrack/issue/codio-9306 * add comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please release a version of pty.js after update nan to 1.8.4 for iojs V2.2.0 build
The text was updated successfully, but these errors were encountered: