Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: a bug with gnus-summary-refer-article?
Date: Wed, 13 Jan 2016 18:10:04 +0900	[thread overview]
Message-ID: <b4m1t9lsv4j.fsf@jpl.org> (raw)
In-Reply-To: <m2h9ihq2xt.fsf@charm-ecran.irisa.fr>

On Wed, 13 Jan 2016 09:49:34 +0100, Alan Schmitt wrote:
> On 2016-01-13 09:50, Katsumi Yamaoka <yamaoka@jpl.org> writes:
[...]
>> 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'm not a nnimap user much less a nnimap expert, sorry.  But...

> 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?

Ok, I'll try it with the other back end and different servers.



  reply	other threads:[~2016-01-13  9:10 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
2016-01-13  9:10       ` Katsumi Yamaoka [this message]
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=b4m1t9lsv4j.fsf@jpl.org \
    --to=yamaoka@jpl.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).