From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: ding@gnus.org
Subject: Re: a bug with gnus-summary-refer-article?
Date: Wed, 13 Jan 2016 09:49:34 +0100 [thread overview]
Message-ID: <m2h9ihq2xt.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <b4m4meil2uh.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 13 Jan 2016 09:50:30 +0900")
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
On 2016-01-13 09:50, Katsumi Yamaoka <yamaoka@jpl.org> writes:
> On Sun, 10 Jan 2016 22:21:55 +0100, Alan Schmitt wrote:
>> 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.
> [...]
>> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>> =(nil 32)
>> gnus-summary-mark-article(-1 82)
> [...]
>> gnus-summary-refer-article("52947012.308@cse.gu.se")
>
> I'm not quite sure whether these are helpful questions, but
>
> What is the method of the group (nnml, nnimap, ...) you are in?
nnimap
> What is the method of the group where <52947012.308@cse.gu.se> comes?
nnimap, from another server
> What is the mark the <52947012.308@cse.gu.se> article had?
79, which seems to be 'O'.
> I haven't been able to reproduce such an error so far.
The crux of the error is on line 11110 of gnus-sem.el. When I edebug
this function, it is used twice (once for the existing article in the
group, and once for the newly inserted article). During the second
execution, this line
(setq mark (gnus-request-update-mark gnus-newsgroup-name article mark))
evaluates to nil, I guess because `article' is a negative number or
because the article comes from a group that is on another server. Do you
see this as well?
Thanks,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated January 11, 2016, Mauna Loa Obs.): 401.96 ppm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2016-01-13 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 21:21 Alan Schmitt
2016-01-12 8:00 ` Alan Schmitt
2016-01-13 0:50 ` Katsumi Yamaoka
2016-01-13 8:49 ` Alan Schmitt [this message]
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=m2h9ihq2xt.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).