-
Notifications
You must be signed in to change notification settings - Fork 24
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
Restart the idris compiler after every commmand if it was killed #54
Conversation
according to the node documentation there is a |
@jeremy-w could you take a look at this? |
@process.on 'error', @error | ||
@process.on 'exit', @exited | ||
@process.on 'close', @exited | ||
@process.on 'disconnect', @exited |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like, in place of the connected
property that wasn't working for you, you're watching for the process to die via all the various events?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The connected
property is a bool that should tell if it's connected right now (at least according to the docs). I use killed
now to check if the compiler is running, and only start a new instance if it's not.
The events are used if the compiler crashes or is killed by the user.
Restart the idris compiler after every commmand if it was killed
No description provided.