search

millejoh / emacs-ipython-notebook

Jupyter notebook client in Emacs
http://millejoh.github.io/emacs-ipython-notebook/
GNU General Public License v3.0
1.47k stars 122 forks source link

Command jupyter not found or not executable #601

Closed tbouiller closed 5 years ago

tbouiller commented 5 years ago

I installed ein via MELPA and averything worked fine, but then I closed emacs and when I reoppened it next time and tried to run ein by doing M-x run:ein I get this error message : Command jupyter not found or not executable It's pretty weird because everything was working fine just before and I cannot find any similar issues. The debugger outputs this but I don't get what's not working `Debugger entered--entering a function:

entropy43 commented 5 years ago

Not to be facetious but I’m assuming you have installed Jupyter already and you’re able to open a notebook in your browser? (ie $ jupyter notebook from your terminal).

Can you see if you can try the indirect method of opening a notebook in your browser (per the command line instruction above) and then see if you can get things running in emacs with:

M-x ein:notebooklist-login

This will then prompt you to specify the port your Jupyter notebook is running on (should be 8888 by default) and, depending on platform and version, then perhaps ask you for the key / password.

On Mon, 14 Oct 2019 at 19:05, Theophile Bouiller notifications@github.com wrote:

I installed ein via MELPA and averything worked fine, but then I closed emacs and when I reoppened it next time and tried to run ein by doing M-x run:ein I get this error message : Command jupyter not found or not executable It's pretty weird because everything was working fine just before and I cannot find any similar issues. The debugger outputs this but I don't get what's not working `Debugger entered--entering a function:

  • ein:run(nil "/.emacs.d/elpa/ein-20191012.1337/" nil

    f(compiled-function (buffer url-or-port) #<bytecode 0x17d66d9>))

    funcall-interactively(ein:run nil "/.emacs.d/elpa/ein-20191012.1337/" nil #f(compiled-function (buffer url-or-port) #<bytecode 0x17d66d9>)) call-interactively(ein:run record nil) command-execute(ein:run record) execute-extended-command(nil "ein:run" "ein:run") funcall-interactively(execute-extended-command nil "ein:run" "ein:run") call-interactively(execute-extended-command nil nil) command-execute(execute-extended-command) recursive-edit() debug() funcall-interactively(debug) call-interactively(debug record nil) command-execute(debug record) execute-extended-command(nil "debug" "debug") funcall-interactively(execute-extended-command nil "debug" "debug") call-interactively(execute-extended-command nil nil) command-execute(execute-extended-command) `

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/millejoh/emacs-ipython-notebook/issues/601?email_source=notifications&email_token=AGDW7ZFSZMIE5OS7HFQPABLQOQR3ZA5CNFSM4JAL3AF2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HRQTJ6Q, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDW7ZD6D37QV3I5NR4VLRLQOQR3ZANCNFSM4JAL3AFQ .

tbouiller commented 5 years ago

Ah yes I should have metionned it but jupyter notebook does run normally in the browser, but I tried what you said and it does work by running a notebook beforehand and loging in into emacs. It's just a bummer that I cannot launch one directly in emacs

millejoh commented 5 years ago

This behavior is mostly described in the documentation. The variable you want to look at is ein:jupyter-default-server-command.

I suggest you set that variable to the absolute path to your jupyter executable (explicit is better than implicit).

tbouiller commented 5 years ago

So i've tried setting different variables for ein:jupyter-default-server-command, and omitting ein:jupyter-server-use-subcommand but it seems that whatever I throw in, the command does not get recognised, which is troubling because it was working at some point.

millejoh commented 5 years ago

What happens if you try to call jupyter notebook from inside ansi-term (or other equivalent)? Other places to look for clues would be the *ein:log-all* and *ein:jupyter-server* buffers.