From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-contrib: org-eldoc has an autload, but is incompatible with modern emacs. [9.6.8 (release_9.6.8-3-g21171d @ /usr/share/emacs/30.0.50/lisp/org/)]
Date: Tue, 26 Dec 2023 20:13:49 +0800 [thread overview]
Message-ID: <87edf988j1.fsf@laptop.lockywolf.net> (raw)
In-Reply-To: <874jg5mack.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Vladimir Nikishkin <lockywolf@gmail.com> writes:
>
>> So, this might not actually be the case.
>> I am getting a lot of org-element-cache errors recently, and I don't
>> seem to be able to find what triggers them to appear.
>> The error message is always the same,
>> "Invalid search bound (wrong side of point)"
>>
>> Any ideas on how to debug this?
>
> If you are using the latest main, you can set `debug-on-error' to t.
> Then, you will see the backtrace of the error that you can share.
Did that, but it's not very useful:
#+begin_src elisp
Debugger entered--Lisp error: (error "Invalid search bound (wrong side of point)")
org-element-paragraph-parser(23 (23))
org-element--current-element(23 element nil nil)
org-element--parse-to(573 nil nil)
org-element--cache-process-request([552 552 3010 22 nil 1] nil 3010 nil nil nil)
org-element--cache-sync(#<buffer index.org> 3010)
org-element-at-point()
org-eldoc-get-src-lang()
org-eldoc-documentation-function(#f(compiled-function (string &rest plist) #<bytecode 0x138508dae21a79a6>))
eldoc-documentation-default()
eldoc--invoke-strategy(nil)
eldoc-print-current-symbol-info()
#<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_12>()
apply(#<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_12> nil)
timer-event-handler([t 0 0 500000 nil #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_12> nil idle 0 nil])
#+end_src
The beginning of the call stack may be different, but the deep levels,
with "org-element--parse-to" are always more or less the same, and
produce the same error.
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
next prev parent reply other threads:[~2023-12-26 12:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 3:51 [BUG] org-contrib: org-eldoc has an autload, but is incompatible with modern emacs. [9.6.8 (release_9.6.8-3-g21171d @ /usr/share/emacs/30.0.50/lisp/org/)] Vladimir Nikishkin
2023-10-20 7:37 ` Ihor Radchenko
2023-10-20 7:39 ` Vladimir Nikishkin
2023-10-20 7:49 ` Ihor Radchenko
2023-11-10 1:22 ` Vladimir Nikishkin
2023-12-26 9:27 ` Vladimir Nikishkin
2023-12-26 12:12 ` Ihor Radchenko
2023-12-26 12:13 ` Vladimir Nikishkin [this message]
2023-12-26 12:23 ` Ihor Radchenko
2023-12-26 12:26 ` Vladimir Nikishkin
2023-12-26 12:34 ` Vladimir Nikishkin
2023-12-26 13:22 ` Ihor Radchenko
2023-12-26 13:25 ` Vladimir Nikishkin
2023-12-26 13:31 ` Ihor Radchenko
2023-12-26 13:59 ` Vladimir Nikishkin
2023-12-26 14:33 ` Ihor Radchenko
2023-12-26 14:45 ` Vladimir Nikishkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edf988j1.fsf@laptop.lockywolf.net \
--to=lockywolf@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).