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 11:33:48 +0100 [thread overview]
Message-ID: <m24mehpy43.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <b4mvb6xrflz.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 13 Jan 2016 18:30:32 +0900")
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
On 2016-01-13 18:30, Katsumi Yamaoka <yamaoka@jpl.org> writes:
> On Wed, 13 Jan 2016 18:10:04 +0900, Katsumi Yamaoka wrote:
>> Ok, I'll try it with the other back end and different servers.
>
> After having done some tests, I got to guess that it might arise
> with only nnimap. So, I'd like to ask nnimap people to reproduce
> and fix it:
>
> <http://thread.gmane.org/gmane.emacs.gnus.general/86583/focus=86599>
Thank you for your tests.
After a little more debugging here, it seems that what happens is that
the following configuration is important for this to break:
(setq gnus-refer-article-method
'(current
(nnir "nnimap:inria")
(nnir "nnimap:local")))
The `gnus-request-update-mark' function works well for nnimap (as there
is no corresponding function, so the initial mark is returned), but it
seems to be problematic with nnir. I cannot edebug it further because
`nnir-request-update-mark' is a deffoo, and I don’t know how to debug
those.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated January 12, 2016, Mauna Loa Obs.): 401.82 ppm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2016-01-13 10:33 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
2016-01-13 9:30 ` Katsumi Yamaoka
2016-01-13 10:33 ` Alan Schmitt [this message]
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=m24mehpy43.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).