GNU bug report logs - #48664
28.0.50; gnus stuck with error: (wrong-type-argument number-or-marker-p nil)

Previous Next

Package: emacs;

Reported by: Pankaj Jangid <pankaj <at> codeisgreat.org>

Date: Wed, 26 May 2021 07:43:02 UTC

Severity: normal

Tags: moreinfo

Found in version 28.0.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


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

From: Pankaj Jangid <pankaj <at> codeisgreat.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 48664 <at> debbugs.gnu.org
Subject: Re: bug#48664: 28.0.50; gnus stuck with error: (wrong-type-argument
 number-or-marker-p nil)
Date: Fri, 28 May 2021 16:23:21 +0530
Lars Ingebrigtsen <larsi <at> gnus.org> writes:

>> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>>   <=(nil 2)
>>   gnus-get-unread-articles(2 t)
>
> Try loading the uncompiled version of gnus-start.el -- that'll give a
> more detailed backtrace.

It is a bit inconsistent. Now it is working with the latest commits. And
I am not sure, as of now, which commits have caused it. Tried a few. I
will try the above suggestion if I observe it again.

By any chance could this be related to modus-theme changes. It is
recently upgraded. And the fonts are looking really weird when I load it
from init file. I’ll file a separate bug for this. But why I am saying
this is because I have disabled modus-theme and after that I have not
faced this issue.






This bug report was last modified 2 years and 313 days ago.

Previous Next


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