Vladimir Nikishkin <lockyw...@gmail.com> writes: >> May you elaborate about incompatibility? >> > > Yes. With org-eldoc loaded, and having a property '#+date: unpublished' > in an org file, I am having the '*Messages*' buffer filled with > #+begin_src elisp > ⛔ Warning (org-element-cache): org-element--cache: Org parser error in > 2015_Passwords.org.rclignore::53653. Resetting. > The error was: (error "Invalid search bound (wrong side of point)") > Backtrace: > " backtrace-to-string(nil) > org-element-at-point()
This has nothing to do with eldoc. If you can reproduce this problem consistently, may you create a minimal example as described in https://orgmode.org/manual/Feedback.html#Feedback ? >> That would constitute incompatible change for the existing users. >> Although, autoload may cause org-eldoc to be loaded for users of >> org-contrib, who are not interested in org-eldoc. >> What we might do as a compromise is removing the autoload cookie only >> and leaving the (add-hook ...) to be executed upon (require 'org-eldoc). > > Yes, maybe that is even better. Why would one (require 'org-eldoc) with > no intention of using it? Fixed, on master. https://git.sr.ht/~bzg/org-contrib/commit/6e208c87bf6ede9251c9c5733b81b004b1e44966 As for `require', it is not so simple. Things like C-h f can trigger loading libraries. But addressing such peculiarities is beyond the level of maintenance we can provide for org-contrib. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
