From: Uwe Brauer <oub@mat.ucm.es>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Warning (org-element-cache): org-element--cache: Org parser error in suma-por-fila.tex::1585. Resetting. [9.5.3 (release_9.5.3-465-gd7dc62 @ /home/oub/emacs/site-lisp/packages/org/)]
Date: Mon, 02 May 2022 08:41:25 +0200 [thread overview]
Message-ID: <87y1zkwi5m.fsf@mat.ucm.es> (raw)
In-Reply-To: 871qxcv3xt.fsf@localhost
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
>>> "IR" == Ihor Radchenko <yantar92@gmail.com> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>>> This is most likely done by your personal customisation or by
>>> third-party package (`link-message' function).
>>
>> I see, most likely orglink (available in melpa)
>> ;; Homepage: https://github.com/tarsius/orglink
>>
>> Was the culprit, I upgraded the package and have not seen that message so far anymore.
> I am not sure. I searched through commit history of orglink and there is
> no instance of org-element-context.
> So, beware that the observed issue might be related to some other package.
I see, thanks for pointing that out. I run a grep -r in my .emacs.d/elpa
directory and indeed still a lot of packages use that function, but in
my understanding all of them refer to org files. Hm, strange.
I do use a bit old version of org-ref though (since I have difficulties
with the new interface and no time to get acquainted now).
I will try later to dig more into the issue.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
prev parent reply other threads:[~2022-05-02 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 17:38 [BUG] Warning (org-element-cache): org-element--cache: Org parser error in suma-por-fila.tex::1585. Resetting. [9.5.3 (release_9.5.3-465-gd7dc62 @ /home/oub/emacs/site-lisp/packages/org/)] Uwe Brauer
2022-05-02 4:13 ` Ihor Radchenko
2022-05-02 6:12 ` Uwe Brauer
2022-05-02 6:33 ` Ihor Radchenko
2022-05-02 6:41 ` Uwe Brauer [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=87y1zkwi5m.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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).