Hi Ihor:
So if we want to determine the Org type of an element outside of an Org
buffer (when using org-type minor modes for example), how would we change
this 'let' code:
(let* ((context
;; Only consider supported types, even if they are not
;; the closest one.
(org-element-lineage
;; Next line can trigger an error when `looking-at' is called
;; with a `nil' value of `org-complex-heading-regexp'.
(org-element-context)
'(clock footnote-definition footnote-reference headline
inlinetask link timestamp)
t))
(type (org-element-type context))
...)
Thanks,
Bob
On Sat, Oct 22, 2022 at 3:53 AM Ihor Radchenko <yanta...@posteo.net> wrote:
> Gregor Zattler <g...@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>
>
>
