From: Ihor Radchenko <email@example.com>
To: Eugene Rakhmatulin <firstname.lastname@example.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: Thu, 03 Feb 2022 20:42:44 +0800 [thread overview]
Message-ID: <87o83oyvcr.fsf@localhost> (raw)
Eugene Rakhmatulin <email@example.com> writes:
> On Tue, Feb 1, 2022 at 9:54 PM Eugene Rakhmatulin <firstname.lastname@example.org> wrote:
>> On Fri, Jan 28, 2022 at 10:16 PM Ihor Radchenko <email@example.com> wrote:
>> > This is a big strange.
>> > Can you try to repeat the same steps, but removing the contents of
>> > org-persist-directory before opening Emacs?
> Well, that happened again. See the backtrace below.
> What I did:
> 1. Removed org-persist-directory folder yesterday
> 2. Did a quick capture of task (with some embedded checklist) on my
> main computer today
> 3. Went to another computer and refreshed Agenda there, got
> questionmarks (org directory is synced between both via iCloud)
> 4. Went to the problematic buffer and ran backtrace command there,
> saved the output
> If I delete org-persist-directory again, the questionmarks disappear
Something is strange about your backtrace. If auto-revert updates
changed buffer, the change should be logged like
org-element-cache diagnostics(inbox.org): Phase 0
org-element-cache diagnostics(inbox.org): org-element-cache: Processing request ...
org-element-cache diagnostics(inbox.org): Syncing down to nil-nil
org-element-cache diagnostics(inbox.org): nil is about to modify text...
I do not see it in your backtrace, which implies that the buffer was not
reverted or that you ran backtrace multiple times.
Can you try again next time you see the questionmarks and also provide
the output of M-: (pp org-element--cache) executed in the problematic
Also, I have made changes in saving cache between Emacs sessions. An
Org mode update might help if you are lucky.
next prev parent reply other threads:[~2022-02-03 13:01 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
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 [this message]
2022-02-20 7:29 ` Ihor Radchenko
2022-03-10 23:38 ` Eugene Rakhmatulin
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 \
* 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).