-
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
Builtin Org mode (8.x) breaking Spacemacs Org mode (9.x) #8414
Comments
After some spacemacs restarts, the results seem to improve. Would there be some kind of But even when all org-packages are loaded from elpa, the org-babel evaluation disabled error persists. Maybe the problem could be that
So org-plus-contrib arrives nearly last ! . Although it seems that an effort is being made in Related posts: |
My gist is really a WIP and I just added interesting results there. They show that , on a fresh install of develop branch:
|
\o/ SUCCESS with org-babel evaluation !!after specific recompilation of |
Thank you for your work on this :) |
@RockyRoad29 Your issue seems to be fixed, if so you can close this issue :-) |
Is this supposed to be sorted now? Had a couple of new spacemacs installs over the last month or so and still getting the built-in org mode loading (And thus, stuff breaking 😢) |
My bad. After searching my |
@syl20bnr Actually I had kind of fixed it for myself working on the dev branch, which let me forget about this issue. Today I attempted an upgrade from the spacemacs home buffer (forgot about the dev branch), and all org-mode went in a mess again. I tried again from a clean install of the master branch (- Emacs: 25.3.1 - Spacemacs: 0.200.10) but the problem is still there. Batch compilation doesn't really help. I feel there should be something to do about compilation order. But I don't have much time to put in that now. |
I didn't find this information easily, so I'm posting it here since it's the second time I need to find it. To fix this, because I'm using multiple branches (mostly because I didn't clean up after switching to the develop/ branch), I needed to, from the root of the spacemacs git repo:
Then from emacs:
|
Should be fixed in develop, please verify. |
Thank you @syl20bnr . I upgraded last night to commit 723604d . As I figured out last weeks, org babel errors can often be solved by calling e.g. I enjoyed then the |
Since, I got annoyed with org-table bug I can see in many places this advice of removing What does help:spacemacs/recompile-elpa actually do ? (byte-recompile-directory package-user-dir nil t) Would there be a misunderstanding of help:byte-recompile-directory ?
Is called with I think it is Knowing that many problems arise from site emacs packages shadowing spacemacs (let (
(org-base-dir (file-name-directory (find-library-name "org")))
)
(if
(string-match (concat (file-name-as-directory package-user-dir) "org-plus-contrib") (find-library-name "org"))
(byte-recompile-directory org-base-dir 0 nil)
(message "unexpected location for org package : %s" org-base-dir)
)
) Deleting all .elc files seems to me as increasing the risk of getting packages Hoping this can help. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
Description
Builtin Org mode (8.x) breaking Spacemacs Org mode (9.x)
Some org packages are loaded from
org-plus-contrib
,which currently depends on org version 9.0.x ,
while some other are loaded from the built-in emacs,
which is usually 8.x .
This causes many incompatibilities due e.g. to changes
of variable to functions, like
org-link-types
( change ),or
org-babel-check-confirm-evaluate
Reproduction guide 🪲
*scratch*
in lisp interaction mode.Yes, it looks like
(org-version)
is lying !!!However, the responsability of loading the libs properly comes to Spacemacs
I think.
I think that
#'find-lisp-object-file-name
is what is usedin
#'describe-function
but it didn't work as expected forfunctions from
'ob
. Anyway there is some discrepancy around.Observed behaviour: 👀 💔
Some actions in org-mode fail and you'd see messages like:
(see more on #8074') .
Sometimes, I managed to get rid of these
org-link-types
errors, but then (with some recompilation voodoo) I found that source block evaluation was failing (packageob
: org-babel):(see more on #7641)
Expected behaviour: ❤️ 😄
I'd expect that all org modules would be loaded from elpa
(or none at worst) to ensure version comptability between libraries.
Details about org libraries
I wrote a few helpers to explore the loaded libraries and here are
some results:
System Info 💻
The text was updated successfully, but these errors were encountered: