Skip to content
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

Handle SIGQUIT #102

Open
jasontwong opened this issue Aug 25, 2016 · 2 comments
Open

Handle SIGQUIT #102

jasontwong opened this issue Aug 25, 2016 · 2 comments
Labels
Milestone

Comments

@jasontwong
Copy link

For some reason the process doesn't quit with Ctrl + \ but does with Ctrl + c.

SIGQUIT is the dump core signal. The terminal sends it to the foreground process when the user presses ctrl-\. The default behavior is to terminate the process and dump core, but it can be caught or ignored. The intention is to provide a mechanism for the user to abort the process.
@kenwheeler kenwheeler added the Bug label Aug 26, 2016
@vernondegoede
Copy link

@kenwheeler For some reason the following piece of code isn't being recognised by Node. Also, listening for the 'C-' event doesn't work since the backslash will need to be escaped (and isn't recognised as a valid key combination anymore).

process.on("SIGQUIT", function () {
  process.exit(0);
});

Other terminal apps, like Node itself, don't quit with Ctrl + \ either. Is this still a valid way to quit processes?

@jasontwong
Copy link
Author

express and webpack --watch work with Ctrl + \. So does irb, yes, grep, etc. But you are correct that the node REPL does not support it. Maybe it should be handled upstream on node?

@kenwheeler kenwheeler added this to the 2.0 milestone Jan 15, 2018
@ryan-roemer ryan-roemer modified the milestones: 2.0, 3.0 May 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants