Skip to content
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

progn: Symbol's function definition is void: when-let #133

Closed
cheremin opened this issue Jun 15, 2019 · 5 comments
Closed

progn: Symbol's function definition is void: when-let #133

cheremin opened this issue Jun 15, 2019 · 5 comments

Comments

@cheremin
Copy link
Contributor

I've got those errors in last version (20190613) while evaluating orgmode scriptlets. It appears constantly, after each try to evaluate. I'm not sure is it due to new version, but it seems likely.

@nnicandro
Copy link
Collaborator

Are you using compiled versions of the source code? If you evaluate (require 'subr-x) and the problem goes away it is most likely because the compiled versions of the sources are not being used.

@cheremin
Copy link
Contributor Author

cheremin commented Jun 16, 2019

Well, I've installed package from melpa, with (use-package jupyter :ensure t) -- i.e. I don't know are there compiled versions. But I've tried (require 'subr-x) after fresh emacs restart, and indeed, Symbol's function definition is void goes away. (I've noted same does happen if I run jupyter-run-repl)

But new problem appears instead: now block of code is executed, but results are just GUID:
: 1 - 39e2567f-faec-46b6-a731-893b969222ec
and minibuffer state error in process sentinel: Search failed: "b5d6bfb3-e37f-4c58-a2e5-edcf1ad2430f"
I've noted, GUIDs in document and in error message are off by one: i.e. next time I try to run same block I'll get error about not being able to find "39e2567f-faec-46b6-a731-893b969222ec", while this ID in document are already replaced with the next one.

@cheremin
Copy link
Contributor Author

cheremin commented Jun 16, 2019

Ok, seems like I've solved 2-nd issue: looks like ob-ipython which I have installed and used before, somehow conflicts with emacs-jupyter. I'm not so familiar with emacs debugging to got all the details, but the result processing for jupyter-python source block is somehow go through ob-ipython code. Uninstalling ob-ipython solved the issue.

If it is not my-only issue, it may worth to note on wiki, since, I think, many emacs-jupyter users may come from using ob-ipython beforehand

@nnicandro
Copy link
Collaborator

It would be a good idea to add some note in the documentation about incompatibility with ob-ipython I think someone has had a similar issue in the past. Would you like to make a note in the documentation, under the =org-mode= source blocks section, and submit a pull request?

@cheremin
Copy link
Contributor Author

It would be a good idea to add some note in the documentation about incompatibility with ob-ipython I think someone has had a similar issue in the past. Would you like to make a note in the documentation, under the =org-mode= source blocks section, and submit a pull request?

Sorry for a delay
Yes, sure, here is my version: #135

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants