From: Ihor Radchenko <yantar92@posteo.net>
To: Gregor Zattler <grfz@gmx.de>
Cc: emacs-orgmode@gnu.org, hyperbole-users@gnu.org
Subject: Re: [BUG] hyperbole action key on path name results in org-element-cache warning [9.6-pre (release_9.5.5-997-ge58bd0 @ /home/grfz/src/org-mode/lisp/)]
Date: Sat, 22 Oct 2022 07:43:47 +0000 [thread overview]
Message-ID: <87czak1ex8.fsf@localhost> (raw)
In-Reply-To: <87h6zwbylo.fsf@no.workgroup>
Gregor Zattler <grfz@gmx.de> writes:
> Dear org-mode and hyperbole developers, hitting hyperbole's
> action-key with point in "~/src/org-mode/contrilb/lisp" in a
> *Pp Eval Output* buffer holding my complete load-path
> resulted in this org-element--cache warning:
>
> ■ Warning (org-element-cache): org-element--cache: Org parser error in *Pp Eval Output*::5288. 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()
This is a hyperbole bug.
The latest version of Org no longer supports calling
org-element-at-point in non-Org buffers. Previously it worked by
accident and did not throw an error.
I recommend using regexp constants from Org to match against org-like
constructs outside Org mode buffers.
--
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>
next prev parent reply other threads:[~2022-10-22 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 22:28 [BUG] hyperbole action key on path name results in org-element-cache warning [9.6-pre (release_9.5.5-997-ge58bd0 @ /home/grfz/src/org-mode/lisp/)] Gregor Zattler
2022-10-22 7:43 ` Ihor Radchenko [this message]
2022-12-11 18:13 ` Robert Weiner
2022-12-12 11:47 ` 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
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=87czak1ex8.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=grfz@gmx.de \
--cc=hyperbole-users@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 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).