org-mode errors

[jvillasante]

I get this error all over the place when using org-mode

user-error: An element cannot be parsed line #

I also can't set auto-fill on org-mode, can't break lines... almost unusable....
Thinking about getting back to vim, I expend more time configuring emacs/spacemacs than actually doing my job!!!

[d12frosted]

@jvillasante it would be a good starting point to share the output of SPC h d s. Steps to reproduce wouldn't hurt as well. Thanks :)

[StreakyCobra]

And as for every bug you can try the following actions:

• Update Spacemacs and restart
• Update your packages and restart
• Move .emacs.d/elpa to .emacs.d/elpa-old and restart (if this cause any problem you can still move back the old folder)
• Try to reproduce the bug without your .spacemacs

[jvillasante]

I'm sorry, I was angry yesterday. I just convinced everyone at work to write our internal documentation in org-mode and then it all started to fail. It was a rush post. Both emacs and spacemacs are great software. I solved the issue adding this to my dotspacemacs/user-init. I don't understand the why but somehow it now works.

  (with-eval-after-load 'org
    ;; org problems
    (setq org-planning-line-re "")
    (setq org-clock-line-re "")
    )

[StreakyCobra]

If you don't set these lines, what are the values of these variables?

org-clock-line-re is a variable defined in `org.el'.
Its value is "^[    ]*CLOCK:"

org-planning-line-re is a variable defined in `org.el'.
Its value is "^[    ]*\\(\\(?:CLOSED\\|DEADLINE\\|SCHEDULED\\):\\)"

[jvillasante]

If I don't define those variables myself then they not exists at all. I just defined them as you said and everything keeps working ok.

  (with-eval-after-load 'org
    ;; org problems
    (setq org-planning-line-re "^[    ]*\\(\\(?:CLOSED\\|DEADLINE\\|SCHEDULED\\):\\)")
    (setq org-clock-line-re "^[    ]*CLOCK:")
    )

[StreakyCobra]

These variables are defined by org-plus-contrib. Do you have the org layer enabled in your .spacemacs? Can you try what explained here. Also what is the result of M-x org-version RET?

[d12frosted]

Also, as I said, SPC h d s :)

[namdnguyen]

@jvillasante did you also try moving out or deleting your ~/.emacs.d/elpa and restarting? I also had some errors with those same variables with the last org-plus-contrib update. Org-capture was giving me errors as well as M-RET to make a new list entry. Removing my org folders and restarting fixed them for me with out having to set any variables.

I was initially tipped off by this issue.

[haruhi-s]

Same thing here, my org-version is 8.3.6.

[github-actions]

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!