From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: Re: more on the wrong Group unread counts
Date: Mon, 18 Oct 2010 16:54:21 -0400 [thread overview]
Message-ID: <m3hbgji5m2.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <m3eibnwboo.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 18 Oct 2010 21:19:51 +0200")
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> James Cloos <cloos@jhcloos.com> writes:
>> As you can see, Group should show either 4 or 5 unread articles (5
>> exist, 4 are unread), but it instead claimed over 200, probably the
>> difference between the largest and smallest UID values returned by
>> the UID FETCH FLAGS call.
LMI> What was the "FETCH FLAGS" command that Gnus issued?
133397 SELECT "apps-devel@webmproject.org"
133398 UID FETCH 1:* FLAGS
and then I think this was when I entered the group:
133399 UID FETCH 377:611 (UID RFC822.SIZE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref To Newsgroups)])
For completeness sake, the read and write are:
read(0, "133397 SELECT \"apps-devel@webmproject.org\"\r\n", 4096) = 44
write(5, "* 5 EXISTS\r\n", 12) = 12
write(5, "* 4 RECENT\r\n", 12) = 12
write(5, "* FLAGS (\\Seen \\Answered \\Deleted \\Flagged \\Draft)\r\n", 52) = 52
write(5, "* OK [PERMANENTFLAGS (\\Seen \\Answered \\Deleted \\Flagged \\Draft)]\r\n", 66) = 66
write(5, "* OK [UIDNEXT 612] Predicted next UID\r\n", 39) = 39
write(5, "* OK [UIDVALIDITY 47581] UID value\r\n", 36) = 36
write(5, "* OK [UNSEEN 2] first unseen message\r\n", 38) = 38
write(5, "133397 OK [READ-WRITE] SELECT completed\r\n", 41) = 41
read(0, "133398 UID FETCH 1:* FLAGS\r\n", 4096) = 28
write(5, "* 1 FETCH (FLAGS (\\Seen) UID 376)\r\n* 2 FETCH (FLAGS (\\Recent) UID 608)\r\n* 3 FETCH (FLAGS (\\Recent) UID 609)\r\n* 4 FETCH (FLAGS (\\Recent) UID 610)\r\n* 5 FETCH (FLAGS (\\Recent) UID 611)\r\n", 183) = 183
write(5, "133398 OK UID FETCH completed\r\n", 31) = 31
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2010-10-18 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 9:58 James Cloos
2010-10-18 19:19 ` Lars Magne Ingebrigtsen
2010-10-18 20:54 ` James Cloos [this message]
2010-10-18 22:56 ` 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=m3hbgji5m2.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--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).