From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: double SELECT again
Date: Tue, 21 Dec 2010 10:59:03 -0500 [thread overview]
Message-ID: <m38vzji0bk.fsf@jhcloos.com> (raw)
I just noticed that when running M-g on a nnimap group will sometimes
run SELECT twice in a row. I did not see a double SELECT in cases where
the Group buffer unread count remained constant after M-g. But in those
cases where, post M-g, the unread count changed strace showed that SELECT
was done twice:
90941 SELECT "gnash-dev@gnu.org"
* 9 EXISTS
* 9 RECENT
* FLAGS (\Seen \Answered \Deleted \Flagged \Draft)
* OK [PERMANENTFLAGS (\Seen \Answered \Deleted \Flagged \Draft)]
* OK [UIDNEXT 1384] Predicted next UID
* OK [UIDVALIDITY 30194] UID value
* OK [UNSEEN 1] first unseen message
90941 OK [READ-WRITE] SELECT completed
90942 SELECT "gnash-dev@gnu.org"
* 9 EXISTS
* 9 RECENT
* FLAGS (\Seen \Answered \Deleted \Flagged \Draft)
* OK [PERMANENTFLAGS (\Seen \Answered \Deleted \Flagged \Draft)]
* OK [UIDNEXT 1384] Predicted next UID
* OK [UIDVALIDITY 30194] UID value
* OK [UNSEEN 1] first unseen message
90942 OK [READ-WRITE] SELECT completed
90943 UID FETCH 1:* FLAGS
* 1 FETCH (FLAGS (\Recent) UID 1375)
* 2 FETCH (FLAGS (\Recent) UID 1376)
* 3 FETCH (FLAGS (\Recent) UID 1377)
* 4 FETCH (FLAGS (\Recent) UID 1378)
* 5 FETCH (FLAGS (\Recent) UID 1379)
* 6 FETCH (FLAGS (\Recent) UID 1380)
* 7 FETCH (FLAGS (\Recent) UID 1381)
* 8 FETCH (FLAGS (\Recent) UID 1382)
* 9 FETCH (FLAGS (\Recent) UID 1383)
90943 OK UID FETCH completed
(I added a blank line between each write(2) and read(2).)
(Manually converted from strace(1) ouput.)
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next reply other threads:[~2010-12-21 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 15:59 James Cloos [this message]
2011-01-02 6:36 ` 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=m38vzji0bk.fsf@jhcloos.com \
--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).