From: Gregor Zattler <grfz@gmx.de>
To: emacs-orgmode@gnu.org
Subject: [BUG] Warning (org-element-cache): org-element--cache: Org parser error in notmuch-show.el::10751. Resetting. [9.5.4 (release_9.5.4-702-g5a49cc @ /home/grfz/src/org-mode/lisp/)]
Date: Fri, 12 Aug 2022 15:25:19 +0200 [thread overview]
Message-ID: <87pmh53874.fsf@no.workgroup> (raw)
Dear org-mode developers, Ihor,
I just got this warning:
Warning (org-element-cache): org-element--cache: Org parser error in notmuch-show.el::10751. Resetting.
The error was: (error "rx ‘**’ range error")
Backtrace:
" backtrace-to-string(nil)
org-element-at-point()
org-element-context()
hsys-org-link-at-p()
ibtypes::org-link-outside-org-mode()
ibut:at-p()
hbut:at-p()
hkey-execute(nil)
action-key-internal()
action-key()
funcall-interactively(action-key)
command-execute(action-key)
"
Please report this to Org mode mailing list (M-x org-submit-bug-report).
I don't know what triggered it, especially not in an elisp
buffer.
Just an hour ago, or some such, I lowered
org-element--cache-self-verify-frequency from 1.0 to 0.1.
Now I set it to 1.0 again.
I deleted the "current state" part of this template due to
privacy concerns. If you need specific variable values,
please tell me and I will provide them.[1]
Emacs : GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.16.0)
of 2022-08-02
Package: Org mode version 9.5.4 (release_9.5.4-702-g5a49cc @ /home/grfz/src/org-mode/lisp/)
--
Gregor
[1] For me: [[file:~/tmp/2022-08-12-org-element-cache---current-state::current state:]]
next reply other threads:[~2022-08-12 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 13:25 Gregor Zattler [this message]
2022-08-12 13:38 ` [BUG] Warning (org-element-cache): org-element--cache: Org parser error in notmuch-show.el::10751. Resetting. [9.5.4 (release_9.5.4-702-g5a49cc @ /home/grfz/src/org-mode/lisp/)] Ihor Radchenko
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=87pmh53874.fsf@no.workgroup \
--to=grfz@gmx.de \
--cc=emacs-orgmode@gnu.org \
/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.