-
-
Notifications
You must be signed in to change notification settings - Fork 293
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 is not always caught #123
Comments
Hm yes this is a problem/feature with |
This can be solved by overloading the I think that the |
If its nothing serious it doesn't matter so much. An error when trying to exit would only a problem if there is some clean up that would be interrupted by the error. I have no problem pushing CTRL+C twice for now. |
Hey @fonsp, also have a mysterious error propagating. When I tried running the same notebook twice, I got this error:
The reason why I clicked twice on a notebook was because I thought the notebook wasn't running. Maybe something got overloaded somewhere? |
Opening the same notebook twice is fine - you will get two synchronised clients on a shared session. The error is exactly what I meant before - this is a non-error, and it would be nice to prevent HTTP.jl from printing it. |
The common HTTP error messages are now gone (I added the PR fix from Pluto), but the problem that the issue started about is still there |
Should be fixed now |
I don't know it is really important since I wanted to stop Pluto anyway but when I stopped Pluto with CTRL+C the following error message appeared:
The text was updated successfully, but these errors were encountered: