emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Gregor Zattler <grfz@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [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 21:38:31 +0800	[thread overview]
Message-ID: <87edxl8tuw.fsf@localhost> (raw)
In-Reply-To: <87pmh53874.fsf@no.workgroup>

Gregor Zattler <grfz@gmx.de> writes:

> 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")

Thanks for reporting!

>  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()

> I don't know what triggered it, especially not in an elisp
> buffer.

It looks like Hyperbole is calling org-element-context, which does not
work outside org-mode now. Please report to Hyperbole devs.

> 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.

This should be unrelated.

-- 
Ihor Radchenko,
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


      reply	other threads:[~2022-08-12 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 13:25 [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/)] Gregor Zattler
2022-08-12 13:38 ` Ihor Radchenko [this message]

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=87edxl8tuw.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=grfz@gmx.de \
    /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).