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: Sat, 29 Jan 2022 09:17:23 -0800	[thread overview]
Message-ID: <A05C9535-2624-4BA2-9BDC-E4A1CAAD8296@jeffballowe.com> (raw)
In-Reply-To: <8735l7i7q9.fsf@localhost>

Thank you for the very helpful high-level view of things, Ihor. This will help me a lot going forward.


> On Jan 28, 2022, at 18:41 PM, Ihor Radchenko <yantar92@gmail.com> wrote:
> Jeff <jeff@jeffballowe.com> writes:
>> Sorry for the delay responding.
> No problem. This list does not have reddit pacing :)
>> The problem resolved after updating Doom Emacs.
> Great!
>> I’m not sure why it resolved, because the org-mode version remained
>> the same.
> Doom Emacs uses development version of Org mode. As you update, only
> latest commit number in the version is going to change:
> M-x org-version
> Org mode version 9.5.2 (9.5.2-g2c70ca <-- latest commit number
>> 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.
> You may consider Doom Emacs upgrade as slightly more stable compared to
> manual update ahead of other Doom users. This particular problem with
> Org appears because we introduced a major and complex change to Org. It
> is not yet stable. We are fixing incoming bugs as they are reported.
> Things should be more stable in a few months.
> Best,
> Ihor

      reply	other threads:[~2022-01-29 17:19 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
2022-01-29  2:41     ` Ihor Radchenko
2022-01-29 17:17       ` Jeff [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:

  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=A05C9535-2624-4BA2-9BDC-E4A1CAAD8296@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).