emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: David Conner <aionfork@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] (Doom) Consistently seeing "org-element--cache" problems [9.6 (9.6-??-0c9b30e @ /home/dc/.emacs.doom/.local/straight/build-28.0.90/org/)]
Date: Thu, 03 Feb 2022 20:24:49 +0800	[thread overview]
Message-ID: <87r18kyw6m.fsf@localhost> (raw)
In-Reply-To: <CAA_WgJUw6bL0-2FheuEx916yEB7WNXGvNyGciMvVLqwgm_1Cfw@mail.gmail.com>

David Conner <aionfork@gmail.com> writes:

> K, my emacs is >28 and locked to the
> https://GitHub.com/flatwhatson/guide-channel for the pure-gtk emacs build.

> I am working on some other things at the moment. I should be able to create
> a guix environment to test these issues and get around the need to have
> pGTK. It may be in a terminal eMacs though. Is that okay?

Terminal Emacs should not affect things. Different Emacs versions should
not as well. At least, as long as you update Org mode to latest version
from main.

> Also, to test, do I simply run the script that was attached on a vanilla
> emacs session? Should this ensure equivalence in the org session?

I am not sure which script you are referring to. In the previous email I
saw an example Org file and no attachments.

First and consequent loads of Org might make a difference if what you
are seeing is related to persistent cache. I hope it is not. In any
case, please provide more details about the warnings/problems you are


  reply	other threads:[~2022-02-03 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  4:07 David Conner
2022-01-29 15:45 ` Ihor Radchenko
2022-02-02 16:12   ` David Conner
2022-02-03 12:24     ` Ihor Radchenko [this message]
2022-04-17  2:36       ` David Conner
2022-04-17  2:49         ` 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:

  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=87r18kyw6m.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=aionfork@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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