emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>, 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 17:27:03 +0800	[thread overview]
Message-ID: <878r5he2hw.fsf@laptop.lockywolf.net> (raw)
In-Reply-To: <87sf5e8kqr.fsf@laptop.lockywolf.net>


Vladimir Nikishkin <lockywolf@gmail.com> writes:

> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> Vladimir Nikishkin <lockywolf@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 ?
>
> I found and fixed this problem.
> It was actually unrelated to bare org, it was due to my experiments with
> org-ts-mode. Sorry for the confusion.

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?

-- 
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)


  reply	other threads:[~2023-12-26  9:30 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 [this message]
2023-12-26 12:12           ` Ihor Radchenko
2023-12-26 12:13             ` Vladimir Nikishkin
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=878r5he2hw.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).