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

Symbol’s function definition is void: org-dynamic-block-define #176

Closed
greened opened this issue Mar 27, 2019 · 5 comments
Closed

Symbol’s function definition is void: org-dynamic-block-define #176

greened opened this issue Mar 27, 2019 · 5 comments

Comments

@greened
Copy link

greened commented Mar 27, 2019

M-x org-jira-get-issues gives:

Symbol’s function definition is void: org-dynamic-block-define

I can see org-dynamic-block-define exists in my copy of org (org-plus-contrib). I'm sure this is some issue with the way org is set up, but how can I debug this?

@bhipple
Copy link

bhipple commented Mar 27, 2019

I had similar problems last week. I'm not sure how to debug it, but in my case I found removing all of the *.elc files in ~/.emacs.d/.cache/ worked. You likely have some stale org-mode pre-compiled elisp files mixed with newer 9.2 updates that removed a couple functions.

@greened
Copy link
Author

greened commented Apr 11, 2019

Unfortunately that didn't work. I use straight so deleted the entire straight directory and had it re-clone and re-build everything. Same problem.

@greened
Copy link
Author

greened commented Apr 12, 2019

The funny thing is, if I eval-buffer org.el then I don't get the error. I haven't had any other issues with org so I don't know if this is a bug with straight or something else. I would think if org isn't getting initialized properly I'd have other issues.

@ahungry
Copy link
Owner

ahungry commented Apr 16, 2019

Since this appears to be an isolated local/caching issue, i'm going to close this. Thank you for reporting.

@ahungry ahungry closed this as completed Apr 16, 2019
@baerrach
Copy link

baerrach commented Nov 6, 2019

I've migrated to straight, and was having this error.

Deleting the melpa cache directory and restarting fixed it.

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

4 participants