emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Jensen <aaronjensen@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Unregistered buffer modifications detected [9.5 (9.5-g49e2f6 @ /Users/myuser/.emacs.d/straight/29/straight/build/org/)]
Date: Wed, 3 Nov 2021 10:30:22 -0400	[thread overview]
Message-ID: <CAHyO48wRbv_6Uy-46oC6D92+hPMT1UGM-AcWRmTmU9Nn=50vnQ@mail.gmail.com> (raw)
In-Reply-To: <87bl31ea40.fsf@localhost>

On Wed, Nov 3, 2021 at 7:43 AM Ihor Radchenko <yantar92@gmail.com> wrote:
>
> Aaron Jensen <aaronjensen@gmail.com> writes:
>
> > Here is a backtrace. The package it mentions is my own:
> > https://github.com/aaronjensen/emacs-orgonomic and
> > https://github.com/Somelauw/evil-org-mode is mentioned too.
>
> The mentions are ok. Backtrace should mention every command that
> actually changes the buffer.
>
> > Unregistered buffer modifications detected. Resetting.
> > ...
> >  Backtrace:
> > "  backtrace-to-string(nil)
> >   org-element--cache-sync(#<buffer 20211101-journal>)
> >   apply(org-element--cache-sync #<buffer 20211101-journal>)
> >   timer-event-handler([t 0 0 599999 nil org-element--cache-sync
>
> > Backtrace:
> >   org-element-cache diagnostics(20211101-journal): Nothing to remove.
> > No elements in cache after 361. Terminating.
>
> It looks like cache complete the synchronisation successfully, but some
> command bypasses modification detection. Unfortunately, I cannot catch
> the problematic command from backtrace. It acts "stealthily" for cache.
> Is there a specific kind of edit sequence that you did right before the
> warning appeared?
>
> Best,
> Ihor

I don't recall, but I'll view-lossage next time it happens.


  reply	other threads:[~2021-11-03 14:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30 15:17 [BUG] Unregistered buffer modifications detected [9.5 (9.5-g49e2f6 @ /Users/myuser/.emacs.d/straight/29/straight/build/org/)] Aaron Jensen
2021-10-30 15:39 ` Ihor Radchenko
2021-10-30 16:45   ` Aaron Jensen
2021-10-31  2:07     ` Aaron Jensen
2021-10-31  2:55       ` Ihor Radchenko
2021-10-31  2:48     ` Ihor Radchenko
2021-10-31  3:16       ` Aaron Jensen
2021-11-01  0:38         ` Aaron Jensen
2021-11-01 12:50           ` Ihor Radchenko
2021-11-02 23:19             ` Aaron Jensen
2021-11-02 23:32               ` Aaron Jensen
2021-11-03 11:40                 ` Ihor Radchenko
2021-11-03 11:45               ` Ihor Radchenko
2021-11-03 14:30                 ` Aaron Jensen [this message]
2021-11-04  3:18                   ` Aaron Jensen
2021-11-04 14:12                     ` Ihor Radchenko
2021-11-04 17:05                       ` Aaron Jensen
2021-11-12  4:25                         ` Aaron Jensen
2021-11-14  8:01                           ` Ihor Radchenko
2021-11-14 20:10                             ` Aaron Jensen
2021-11-17  6:05                               ` Aaron Jensen
2021-11-17 12:04                                 ` Ihor Radchenko
2021-11-18 14:15                                   ` Aaron Jensen
2021-11-18 14:30                                     ` Ihor Radchenko
2021-11-17 12:20                                 ` Max Nikulin

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='CAHyO48wRbv_6Uy-46oC6D92+hPMT1UGM-AcWRmTmU9Nn=50vnQ@mail.gmail.com' \
    --to=aaronjensen@gmail.com \
    --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).