From: Julien Danjou <julien@danjou.info>
To: ding@gnus.org
Subject: QRESYNC, nnimap and vanished
Date: Thu, 28 Oct 2010 12:19:00 +0200 [thread overview]
Message-ID: <sa3wrp2tyaz.fsf@cigue.easter-eggs.fr> (raw)
Hi,
I imagine this question is more directed to Lars, but maybe others Gnus
hackers can enlighten me. I noticed that when a message is reported as
VANISHED by QRESYNC on a nnimap server, Gnus does not update the number
of total message in the group.
Actually, it seems the current code mark the vanished messages as
`read', which is not really what's happening. I've tried to debug this,
but I'm still trying to understand all the data structure of Gnus nn*
things right now.
So my questions are
1. is that fixable?
2. What's the info structure means. I understand it's
(groupname (method+groupname a-number (ranges) ?? method (somestuff)))
in somestuff I recognize imap keywords like modseq, uidvalidity. What's
the `active' range?
If there's some documentation, please point me at it. Otherwise, if
someone can explain it to me I'd be glad to enhance the code source to
add such a documentation. :)
--
Julien Danjou
// ᐰ <julien@danjou.info> http://julien.danjou.info
next reply other threads:[~2010-10-28 10:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 10:19 Julien Danjou [this message]
2010-10-28 12:16 ` Greg Troxel
2010-10-28 14:55 ` Lars Magne Ingebrigtsen
2010-10-28 16:17 ` Julien Danjou
2010-10-28 21:03 ` Lars Magne Ingebrigtsen
2010-10-28 22:01 ` James Cloos
2010-10-29 23:33 ` Lars Magne Ingebrigtsen
2010-10-30 8:35 ` Steinar Bang
2010-10-29 7:18 ` Steinar Bang
2010-10-29 23:33 ` Lars Magne Ingebrigtsen
2010-10-30 8:32 ` Steinar Bang
2010-10-30 11:13 ` Lars Magne Ingebrigtsen
2010-10-30 12:52 ` Julien Danjou
2010-10-30 16:39 ` Lars Magne Ingebrigtsen
2010-10-30 20:25 ` Dave Goldberg
2010-10-30 20:32 ` Lars Magne Ingebrigtsen
2010-10-30 20:57 ` Julien Danjou
2010-11-08 9:56 ` Julien Danjou
2010-11-08 21:28 ` Lars Magne 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sa3wrp2tyaz.fsf@cigue.easter-eggs.fr \
--to=julien@danjou.info \
--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).