-
Notifications
You must be signed in to change notification settings - Fork 18
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
Feature: Ctrl-c should kill the pending IO and not the full kernel #75
Comments
Long Journey =>
Hard Challenge => |
I see the same behavior that you do. To me it's strange that ctrl-c in the console client even sends a SIGINT to the kernel; it seems like this should behave the same way that clicking 'interrupt' in the web client would (send a shutdown request to the kernel). I would be okay with just treating ctrl-c as a shutdown+restart request. It's not ideal, but it's better than the current behavior. Also as Jonathan pointed out there's no good way to deal with typing ctrl-c when the console code is starting threads other than hooking into the scheduler...and since this is raku, what if the console code is modifying |
It is too hard, plus the same issue appears in rakudo REPL. |
I opened #84 which makes the experience a little better -- I think it's a reasonable solution -- and I haven't seen any negative effects of doing the eval on another thread. |
On a Slow IO, pressing cltr-c should be handled and interupt the IO but not the full kernel.
The roadmap is to copy IPython implementation:
The text was updated successfully, but these errors were encountered: