emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] Warning (org-element-cache): org-element--cache: Warning(XXX.org): (gz/org-agenda-list) Cached element is incorrect in XXX.org. (Cache tic up to date: "yes")   [9.6.1 (release_9.6.1-208-g0c0059 @ /home/YYYY/src/org-mode/lisp/)]
Date: Tue, 07 Feb 2023 13:11:52 +0100	[thread overview]
Message-ID: <87zg9pektz.fsf@no.workgroup> (raw)
In-Reply-To: <877cwtagh1.fsf@localhost>

Hi Ihor,
* Ihor Radchenko <yantar92@posteo.net> [2023-02-07; 10:59 GMT]:
> Gregor Zattler <telegraph@gmx.net> writes:
>> * Ihor Radchenko <yantar92@posteo.net> [2023-02-06; 10:28 GMT]:
>>> Gregor Zattler <telegraph@gmx.net> writes:
>>> Unfortunately, the provided log is incomplete. I cannot deduce anything
>>> useful from it.
>>
>> that's strange, I realized it was shorter than others, but
>> it's all emacs had in it's *Warnings* buffer then.
>
> This is strange. Did the buffer in question happened to be an indirect buffer?

I do not use indirect buffers intentionally.  If an agenda
is an indirect buffer than it may be -- I do not remember
the exact situation, it was happening at the very first
minutes I used emacs after it's startup.

Ciao; Gregor
--
 -... --- .-. . -.. ..--.. ...-.-


  reply	other threads:[~2023-02-07 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06  9:21 [BUG] Warning (org-element-cache): org-element--cache: Warning(XXX.org): (gz/org-agenda-list) Cached element is incorrect in XXX.org. (Cache tic up to date: "yes") [9.6.1 (release_9.6.1-208-g0c0059 @ /home/YYYY/src/org-mode/lisp/)] Gregor Zattler
2023-02-06 10:28 ` Ihor Radchenko
2023-02-07 10:16   ` Gregor Zattler
2023-02-07 10:59     ` Ihor Radchenko
2023-02-07 12:11       ` Gregor Zattler [this message]
2023-02-07 12:18         ` 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:
  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=87zg9pektz.fsf@no.workgroup \
    --to=telegraph@gmx.net \
    --cc=emacs-orgmode@gnu.org \
    /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).