From 7bb7e46e1fe7ee7350f54151124120a4e7c08503 Mon Sep 17 00:00:00 2001 From: Nathaniel Nicandro Date: Thu, 16 May 2019 20:23:29 -0500 Subject: [PATCH] jupyter-start-kernel (jupyter-command-kernel): Change wording of comment --- jupyter-kernel-manager.el | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/jupyter-kernel-manager.el b/jupyter-kernel-manager.el index a5c1dc7..339e162 100644 --- a/jupyter-kernel-manager.el +++ b/jupyter-kernel-manager.el @@ -174,10 +174,10 @@ fatal signal." The --kernel argument of \"jupyter kernel\" is filled in with the `jupyter-kernel-name' of KERNEL and passed as the first argument of the process." - ;; NOTE: On Windows, apparently the "jupyter kernel" command also launches a - ;; new process to start the kernel using something like an exec command, but - ;; exec like commands on Windows launch a new process instead of replacing - ;; the current one which results in the process we start here returning after + ;; NOTE: On Windows, apparently the "jupyter kernel" command uses something + ;; like an exec shell command to start the process which launches the kernel, + ;; but exec like commands on Windows start a new process instead of replacing + ;; the current one which results in the process we start here exiting after ;; the new process is launched. We call python directly to avoid this. (apply #'cl-call-next-method kernel (jupyter-locate-python)