unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "N. Jackson" <njackson@posteo.net>
Cc: yantar92@posteo.net, 75209@debbugs.gnu.org
Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"
Date: Mon, 30 Dec 2024 22:01:30 +0200	[thread overview]
Message-ID: <86zfkdlz39.fsf@gnu.org> (raw)
In-Reply-To: <87zfkddk1l.fsf@Phoenix> (njackson@posteo.net)

> From: "N. Jackson" <njackson@posteo.net>
> Cc: Ihor Radchenko <yantar92@posteo.net>,  75209@debbugs.gnu.org
> Date: Mon, 30 Dec 2024 19:53:42 +0000
> 
> At 21:31 +0200 on Monday 2024-12-30, Eli Zaretskii wrote:
> 
> >> From: "N. Jackson" <njackson@posteo.net>
> >> Date: Mon, 30 Dec 2024 18:48:31 +0000
> >> 
> >>   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"
> 
> > Does the file exist?  If so, what is its content (assuming you can
> > post it here)?
> 
> It exists and currently has the following contents:
> 
>   ;;   -*- mode: lisp-data; -*-
>   (((26482 57035 301257 992000) 26482 60639 74163 973000) ((26482 62694 821331 522000) 26482 62698 583212 450000))

This one seems okay.  I guess we need to wait for the warning and see
then?





  parent reply	other threads:[~2024-12-30 20:01 UTC|newest]

Thread overview: 21+ 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 [this message]
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
2025-01-05 14:18   ` N. Jackson
2025-01-05 17:21     ` Eli Zaretskii
2025-01-06  0:58       ` N. Jackson

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86zfkdlz39.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=75209@debbugs.gnu.org \
    --cc=njackson@posteo.net \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).