GNU bug report logs - #75209
30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"

Previous Next

Full log

Message #95 received at 75209 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: "N. Jackson" <njackson <at> posteo.net>
Cc: yantar92 <at> posteo.net, 75209 <at> debbugs.gnu.org
Subject: Re: bug#75209: 30.0.93; Emacs reader failed to read data in
 "/home/nlj/.cache/org-persist/gc-lock.eld"
Date: Sun, 26 Jan 2025 09:02:28 +0200

> From: "N. Jackson" <njackson <at> posteo.net>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, Ihor Radchenko <yantar92 <at> posteo.net>
> Date: Sun, 26 Jan 2025 03:31:12 +0000
> 
> The following is for completeness (with regards to bug#39824) and
> not directly relevant to the current bug.
> 
> At 19:58 -0500 on Sunday 2025-01-05, N. Jackson wrote:
> >
> > it says in bug#39824 that the broken timer moves farther into the
> > past, but here my broken timer is counting forward
> 
> I have to retract this assertion.  Further observations revealed
> that sometimes it seems the broken timer counts forwards in time and
> sometimes it jumps backwards by days.
> 
> This is because the information displayed by `list-timers' is bogus
> because it prepares the information using `format-seconds' which
> doesn't work properly for negative arguments (bug#75849 [1]).

I think this is a tangent here.  The problem in this bug is not caused
by timers, IMO.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.