You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes it's useful to close a kernel connection without shutting it down (e.g. when connected to a server and it is associated to a notebook). Right now when trying to close a kernel buffer I'm forced to kill the kernel as well. Any workarounds? Also, why this behavior in the first place?
The text was updated successfully, but these errors were encountered:
I think this behavior is there more out of convience to not have to manually kill a kernel. Typically, in my workflow, I just launch kernels associated with one REPL buffer and leave the REPL buffer open for the lifetime of the kernel. I'm only conneected via that REPL buffer so it made sense to shutdown the kernel when the REPL buffer was no longer being used.
It does make sense, as you have pointed out, to not shutdown the kernel when killing a REPL buffer.
No workaround other than fixing the root of the problem. I'll look into it.
Hi!
Sometimes it's useful to close a kernel connection without shutting it down (e.g. when connected to a server and it is associated to a notebook). Right now when trying to close a kernel buffer I'm forced to kill the kernel as well. Any workarounds? Also, why this behavior in the first place?
The text was updated successfully, but these errors were encountered: