From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: ding@gnus.org
Subject: a bug with gnus-summary-refer-article?
Date: Sun, 10 Jan 2016 22:21:55 +0100 [thread overview]
Message-ID: <m2pox9ku4s.fsf@charm-ecran.irisa.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
Hello,
I think I found a bug with `gnus-summary-refer-article'. If I fetch an
article that comes from another group, it gets inserted in the summary
with a number of -1. During the call to `gnus-summary-mark-article', the
following is done
(setq mark (gnus-request-update-mark gnus-newsgroup-name article mark))
which results in mark being nil. This in turn makes the comparisons such
as
(= mark gnus-unread-mark)
fail with a "Wrong type argument: number-or-marker-p, nil".
Here is a trimmed-down backtrace:
Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
=(nil 32)
...
gnus-summary-mark-article(-1 82)
gnus-summary-mark-read-and-unread-as-read()
run-hooks(gnus-mark-article-hook)
apply(run-hooks gnus-mark-article-hook)
gnus-run-hooks(gnus-mark-article-hook)
gnus-article-prepare(-1 nil)
gnus-summary-display-article(-1 nil)
gnus-summary-select-article(nil nil nil -1)
(progn (gnus-summary-select-article nil nil nil number) (throw (quote found) t))
...
gnus-summary-refer-article("52947012.308@cse.gu.se")
call-interactively(gnus-summary-refer-article nil nil)
command-execute(gnus-summary-refer-article)
Is this a known bug?
Thanks,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated December 28, 2015, Mauna Loa Obs.): 402.60 ppm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next reply other threads:[~2016-01-10 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 21:21 Alan Schmitt [this message]
2016-01-12 8:00 ` Alan Schmitt
2016-01-13 0:50 ` Katsumi Yamaoka
2016-01-13 8:49 ` Alan Schmitt
2016-01-13 9:10 ` Katsumi Yamaoka
2016-01-13 9:30 ` Katsumi Yamaoka
2016-01-13 10:33 ` Alan Schmitt
2016-01-13 14:01 ` Alan Schmitt
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=m2pox9ku4s.fsf@charm-ecran.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=ding@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.
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 NNTP newsgroup(s).