emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: "Enrique Kessler Martínez" <qkessler@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-element--cache: Unregistered buffer modifications detected saving org-agenda-files buffers [9.5.3 (9.5.3-g8e69ad @ /Users/enrikes/.emacs.d/straight/build/org/)]
Date: Thu, 26 May 2022 18:14:40 +0800	[thread overview]
Message-ID: <87v8tsmwhb.fsf@localhost> (raw)
In-Reply-To: <CAKt9ijuNZNXjgaKTKJbJF1xhmmYwU65tXuoBkNtTvWBhgdYCsw@mail.gmail.com>

Enrique Kessler Martínez <qkessler@gmail.com> writes:

> I'm running into the Unregistered buffer modifications bug in the past few
> weeks. The current workflow that causes it is:
> - Open org-agenda.
> - Trigger org-save-all-buffers.

Thanks for the report! Could you please share the full text of the
warning? The warning should contain multiple lines with diagnostic


  reply	other threads:[~2022-05-26 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  7:20 [BUG] org-element--cache: Unregistered buffer modifications detected saving org-agenda-files buffers [9.5.3 (9.5.3-g8e69ad @ /Users/enrikes/.emacs.d/straight/build/org/)] Enrique Kessler Martínez
2022-05-26 10:14 ` Ihor Radchenko [this message]
     [not found]   ` <CAKt9ijuee8veStrAXVi_Dzfn1HEEbYkQxdFKC4ODE2qGfw+Y7Q@mail.gmail.com>
2022-05-26 10:29     ` 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=87v8tsmwhb.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=qkessler@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).