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:26:56 +0800 [thread overview]
Message-ID: <CA+A2iZZL4vDh9dRj4FHnuZGM9qAN7_ZjL1_=Ys6LMh1iFgtFeA@mail.gmail.com> (raw)
In-Reply-To: <87y1dhkv9e.fsf@localhost>
On Tue, 26 Dec 2023 at 20:20, Ihor Radchenko <yantar92@posteo.net> wrote:
>
> Vladimir Nikishkin <lockywolf@gmail.com> writes:
>
> >> 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))
>
> Then, you can disable debug-on-error, and add the following to your config:
> (setq org-element--cache-self-verify 'backtrace)
> (setq org-element--cache-self-verify-frequency 1.0)
>
> This will make Org mode produce the detailed parser logs, which you can
> share. (Note that the log may contain parts of your Org file, so you
> may consider sharing privately or obfuscating the logs)
>
> --
> 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>
In which buffer?
--
Yours sincerely, Vladimir Nikishkin
(Sent from GMail web interface.)
next prev parent reply other threads:[~2023-12-26 12:43 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
2023-12-26 12:23 ` Ihor Radchenko
2023-12-26 12:26 ` Vladimir Nikishkin [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+A2iZZL4vDh9dRj4FHnuZGM9qAN7_ZjL1_=Ys6LMh1iFgtFeA@mail.gmail.com' \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.