-
Notifications
You must be signed in to change notification settings - Fork 334
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
Ctrl-C does not abort interactive session #627
Closed
2 tasks done
fatso83 opened this issue
Feb 10, 2020
· 4 comments
· Fixed by xuwei-k/scala-protobuf-docs#103 or igorovic/test-actions#8
Closed
2 tasks done
Ctrl-C does not abort interactive session #627
fatso83 opened this issue
Feb 10, 2020
· 4 comments
· Fixed by xuwei-k/scala-protobuf-docs#103 or igorovic/test-actions#8
Labels
Comments
I tend to agree. npm-check-updates uses the package prompts which does seem to support detection of Ctrl + C. |
There are various ways of achieving this, though one might need to resort to hacks like this for some cases: terkelg/prompts#252 (comment) (actively avoids printing a "Y"). |
Hello, Thank you for your work. |
Fixed and published in |
This was referenced Mar 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have tried several times to test the interactive option for this tool, and very often I want to abort the process and so I press Ctrl-C to send a signal to quit the ongoing operation. This is not respected by the tool, which for some reason has chosen to interpret this as a YES to the current question. This is a highly unconventional choice 😄
I would like to signal listener to interpret Ctrl-C as a signal to do
process.exit(1)
or at least give the user a prompt to quit.The text was updated successfully, but these errors were encountered: