From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: recent problem with IMAP counts
Date: Tue, 03 Jan 2012 22:22:05 +0100 [thread overview]
Message-ID: <m3k458fpmq.fsf@stories.gnus.org> (raw)
In-Reply-To: <muxk46js329.fsf@xemacs.org> (Didier Verna's message of "Tue, 29 Nov 2011 10:14:38 +0100")
Didier Verna <didier@xemacs.org> writes:
> (when (and sequences
> + ;; Check that the process is still alive.
> + (get-buffer-process (nnimap-buffer))
> + (memq (process-status (get-buffer-process (nnimap-buffer)))
> + '(open run))
> (nnimap-possibly-change-group nil server))
Ah, yeah. That's not correct. It checks the process status of the
previous server.
I've pushed out a fix for this now.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2012-01-03 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 9:21 Didier Verna
2011-11-28 10:21 ` Steinar Bang
2011-11-28 11:20 ` Didier Verna
2011-11-28 12:21 ` Eric S Fraga
2011-11-29 6:28 ` Giuseppe 'ferdy' Miceli
2011-11-29 8:17 ` Didier Verna
2011-11-29 9:14 ` Didier Verna
2011-11-29 16:39 ` Steinar Bang
2012-01-03 21:22 ` Lars Magne Ingebrigtsen [this message]
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=m3k458fpmq.fsf@stories.gnus.org \
--to=larsi@gnus.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).