emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeff <jeff@jeffballowe.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Cached element is incorrect in file.org [9.6 (9.6-??-0c9b30e @ /Users/jeffballowe/.emacs.d/.local/straight/build-27.2/org/)]
Date: Fri, 28 Jan 2022 16:46:39 -0800	[thread overview]
Message-ID: <9767BDD5-CA54-412A-AEBD-8067FBD40B71@jeffballowe.com> (raw)
In-Reply-To: <87tudwys3a.fsf@localhost>

Hello, Ihor, and thank you for the very fast reply.

Sorry for the delay responding.

The problem resolved after updating Doom Emacs. I’m not sure why it resolved, because the org-mode version remained the same. I am new to emacs and so also to Doom Emacs. I’m not sure if it is good practice to upgrade Doom Emacs packages I’m using with my Doom configuration or my wait until Doom does that in a Doom Emacs upgrade. 

In any case, problem solved, at least for now.

I love org-mode! It is already a huge part of my life.

Thank you for the help.

> On Jan 22, 2022, at 2:36 AM, Ihor Radchenko <yantar92@gmail.com> wrote:
> Jeff <jeff@jeffballowe.com> writes:
>> What I expected to happen: No error message when editing this file.
>> What, in fact, did happen and happens frequently (no pattern
>> discerned): I get this error message. Everything seems to work ok other than getting this error message frequently.
> Thanks for the report!
> Your Org mode appears to be 1 month old. Can you try to update?
> If update does not solve the problem, can you set
> org-element--cache-self-verify to 'backtrace and share the backtrace
> displayed in the message next time you see it?
> Best,
> Ihor

  reply	other threads:[~2022-01-29  0:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 18:24 [BUG] Cached element is incorrect in file.org [9.6 (9.6-??-0c9b30e @ /Users/jeffballowe/.emacs.d/.local/straight/build-27.2/org/)] Jeff
2022-01-22 10:36 ` Ihor Radchenko
2022-01-29  0:46   ` Jeff [this message]
2022-01-29  2:41     ` Ihor Radchenko
2022-01-29 17:17       ` Jeff

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:

  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=9767BDD5-CA54-412A-AEBD-8067FBD40B71@jeffballowe.com \
    --to=jeff@jeffballowe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* 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


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