From: "N. Jackson" <njackson@posteo.net>
To: 75209@debbugs.gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>, Ihor Radchenko <yantar92@posteo.net>
Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"
Date: Thu, 02 Jan 2025 13:34:10 +0000 [thread overview]
Message-ID: <87v7uxibl9.fsf@Phoenix> (raw)
In-Reply-To: <878qrxgg74.fsf@Phoenix> (N. Jackson's message of "Mon, 30 Dec 2024 18:48:31 +0000")
At 18:48 +0000 on Monday 2024-12-30, N. Jackson wrote:
>
> In the Emacs 30 pretest I have been getting the following warning
> every few days:
>
> Warning (emacs): Emacs reader failed to read data in
> "/home/nlj/.cache/org-persist/gc-lock.eld". The error was: "End of
> file during parsing"
When I woke my system from suspend this morning and switched to the
Emacs session running Gnus, the warning had popped up in that
session -- possibly during suspend or resume.
I immediately looked at gc-lock.eld which contained this:
;; -*- mode: lisp-data; -*-
(((26485 51608 866710 15000) 26486 34929 321731 426000))
(which I guess is again unremarkable).
I checked my buffer list to be absolutely certain that I hadn't
opened any Org Mode files and the only buffers were *Group*,
*scratch*, *Messages*, .newsrc-dribble, and *Warnings*.
The session has one frame and in that frame there was just the Gnus
Group buffer open (until the *Warnings* buffer popped up below it).
With Gnus sitting idle with just it's Group buffer open, I can't see
how it would use any Org Mode features -- or even _do_ anything at
all -- and as I said, no Org Mode (user) files were open in the
session.
next prev parent reply other threads:[~2025-01-02 13:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 18:48 bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld" N. Jackson
2024-12-30 19:31 ` Eli Zaretskii
[not found] ` <87zfkddk1l.fsf@Phoenix>
2024-12-30 20:01 ` Eli Zaretskii
2025-01-01 17:41 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-01 18:52 ` Eli Zaretskii
2025-01-01 21:09 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-31 17:42 ` Ihor Radchenko
[not found] ` <87frm3elkr.fsf@Phoenix>
2024-12-31 19:02 ` Ihor Radchenko
2024-12-31 19:54 ` Eli Zaretskii
2025-01-01 9:42 ` Ihor Radchenko
2025-01-01 12:14 ` Eli Zaretskii
2025-01-02 17:28 ` Ihor Radchenko
2025-01-02 18:48 ` Eli Zaretskii
2025-01-05 10:03 ` Ihor Radchenko
2025-01-05 11:15 ` Eli Zaretskii
2025-01-05 13:18 ` Ihor Radchenko
2025-01-01 15:54 ` N. Jackson
2025-01-02 13:34 ` N. Jackson [this message]
2025-01-05 14:18 ` N. Jackson
2025-01-05 17:21 ` Eli Zaretskii
2025-01-06 0:58 ` N. Jackson
2025-01-06 13:49 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v7uxibl9.fsf@Phoenix \
--to=njackson@posteo.net \
--cc=75209@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yantar92@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.