-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
org-capture throws json-readtable-error #9941
Comments
I'll just add, fwiw:
This is peak-frustration, a bunch of pointless little problems that makes it unusable. Any constructive input appreciated. |
The problem was weird: Jupyter (and pip) needed to be installed. This is a fresh test virtualbox vm and not much has been installed. Below is a different backtrace that gave a clue. I was only able to get it by having a test capture purposely target a non-existent file. So for the future, how do we get emacs to give us better / different backtraces without random testing?
|
I'm getting this issue currently. How come this issue was closed? |
After fiddling around with edebug I get a similar stack trace:
|
@rgrinberg I figured it was just me making a noobie mistake. But now that you mention it, that is not a graceful fail, and not an informative error message. I can re-open if you want, either way works for me. |
I had the same issue which seems to relate to the declaration of ipython in org-babel-load-languages (in emacs init file). What solve the problem for me is:
|
You can set ob-ipython-command to the path of jupyter. e,g |
I'm not using spacemacs, but the problem was also with ipython. Who woulda thunk it... |
@lg2011: Didn't solve the problem for me, still have this problem EDIT: Now it works, I had to solve another issue related to pip. Thanks! |
I think this should be reopened. On devel (f3b6a22) I get Currently I think using an updated ob-ipython with the PR I just opened is a suitable fix, but will have to see what the ob-ipython maintainer thinks... (thanks @vv111y and @lg2011, I probably wouldn't have bothered investigating without what you found out) |
So how to fix this problem? |
Would have never thought that this is related to
|
Is it correct to say that the problem is reported upstream as gregsexton/ob-ipython#156 and that it can be worked around by manually installing Jupyter? If so, we can tag the issue as "Found work-around" and "Reported upstream". |
When I was running emacs on the gui org capture worked, but not in the terminal until I realized that emacs could not find jupyter when running it on the shell. Running |
Reinstalling |
Enabling it makes org-capture fail, see: syl20bnr/spacemacs#9941
I feel like every once in a while I totally forget about this issue and then it bites me in the butt ... happened again |
The best solution for this is to remove https://github.com/benneti/spacemacs-jupyter is a private layer for |
If I may, restate the issue cause I just arrived here and boy...was it confusing what yall were saying is going on. It sounds like org-capture uses (of course) org mode. And if you have python enabled in org mode for executing src blocks, then for some reason it expects jupyter to be available as well? So if you don't have jupyter installed globally (or if - as in my case - you did but then used pyenv to switch to a different python version) you need to To summarize: emacs org-mode which is written in elisp breaks giving you an error about javascript because a particular package in python isn't installed. Do I have that right? 🤣 |
I met the error too:
|
Correct, doing this removes the ADD: For good measure add |
[[https://github.com/syl20bnr/spacemacs/issues/9941][org-capture throws json-readtable-error · Issue #9941 · syl20bnr/spacemacs]]
Description
org-capture throws json-readtable-error. Cannot capture.
Fresh install on a Ubuntu 16.04 virtualbox machine.
Using same dotfile from osx laptop (works there)
Reproduction guide 🪲
SPC a o c
+ select a capture templateObserved behaviour: 👀 💔
"org-capture: Capture abort: (json-readtable-error)"
Expected behaviour: ❤️ 😄
org-capture as usual
System Info 💻
Backtrace 🐾
The text was updated successfully, but these errors were encountered: