emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [BUG] org-contrib: org-eldoc has an autload, but is incompatible wit


From: Vladimir Nikishkin
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
User-agent: mu4e 1.10.7; emacs 29.1.90

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)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]