emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Eugene Rakhmatulin <eugr@eugr.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Questionmarks in org-agenda instead of file names [9.5.2 (9.5.2-g3154c2 @ /Users/eugr/.emacs.d/straight/build/org/)]
Date: Tue, 25 Jan 2022 20:43:59 +0800	[thread overview]
Message-ID: <875yq89e9c.fsf@localhost> (raw)
In-Reply-To: <CACEbr30foBTrDw9wKLog5Z3r9xnei8JuTMKbRe5Fk=WO+gE5VQ@mail.gmail.com>

Eugene Rakhmatulin <eugr@eugr.com> writes:

> When any of the agenda files get updated outside of this instance of
> Emacs (e.g. another editor or in my case Emacs on another machine via a
> synced iCloud Drive folder), questionmarks are displayed instead of a
> file name. That does not always happen, but when it happens, the only
> way to get rid of the questionmarks is to go to the offending file buffer
> and
> run org-element-cache-reset on that buffer. Just rebuilding the agenda
> doesn't help, and even restarting Emacs doesn't help.
>
> After the cache is reset, everything works as expected.

Thanks for the report!

Can you try the following:
1. (setq org-element--cache-self-verify 'backtrace) in your init.el
   before loading org
2. Do whatever it takes to get question marks as category in agenda
3. Go to the problematic Org buffer and run
   M-: (org-element--cache-warn "Backtrace") <RET>
4. Send the contents of the warning message here.

Best,
Ihor


  reply	other threads:[~2022-01-25 13:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 16:49 Eugene Rakhmatulin
2022-01-25 12:43 ` Ihor Radchenko [this message]
2022-01-25 17:19   ` Eugene Rakhmatulin
2022-01-29  6:21     ` Ihor Radchenko
2022-02-02  5:54       ` Eugene Rakhmatulin
2022-02-02 19:20         ` Eugene Rakhmatulin
2022-02-03 12:42           ` Ihor Radchenko
2022-02-20  7:29           ` Ihor Radchenko
2022-03-10 23:38             ` Eugene Rakhmatulin

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=875yq89e9c.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eugr@eugr.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).