From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48664@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <m2r1hrjfj2.fsf@codeisgreat.org> (raw)
In-Reply-To: <87tumnwhqv.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 28 May 2021 07:27:04 +0200")
Lars Ingebrigtsen <larsi@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.
next prev parent reply other threads:[~2021-05-28 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 7:41 bug#48664: 28.0.50; gnus stuck with error: (wrong-type-argument number-or-marker-p nil) Pankaj Jangid
2021-05-26 11:56 ` bug#48664: It is working Pankaj Jangid
[not found] ` <handler.48664.D48664.16220302066697.notifdone@debbugs.gnu.org>
2021-05-27 4:33 ` bug#48664: closed (It is working) Pankaj Jangid
2021-05-27 7:54 ` Julien Cubizolles
2021-05-28 5:27 ` bug#48664: 28.0.50; gnus stuck with error: (wrong-type-argument number-or-marker-p nil) Lars Ingebrigtsen
2021-05-28 10:53 ` Pankaj Jangid [this message]
2022-07-15 10:38 ` Lars Ingebrigtsen
2022-07-16 2:58 ` Pankaj Jangid
2022-07-16 10:38 ` Lars Ingebrigtsen
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=m2r1hrjfj2.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=48664@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).