From: Florian Ragwitz <rafl@debian.org>
To: ding@gnus.org
Subject: Re: nnimap closing connections on gnus-group-suspend
Date: Mon, 27 Sep 2010 14:22:35 +0200 [thread overview]
Message-ID: <8739sve5pw.fsf@tardis.home.perldition.org> (raw)
In-Reply-To: <yb0lj6n8mku.fsf@dod.no> (Steinar Bang's message of "Mon, 27 Sep 2010 13:14:57 +0200")
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
Steinar Bang <sb@dod.no> writes:
>>>>>> Florian Ragwitz <rafl@debian.org>:
>> On gnus-group-suspend, the old nnimap seems to have kept open the
>> connection to the IMAP server, whereas the new one closes them and
>> reconnects when Gnus is started the next time.
>
> FWIW I think the new behaviour is the correct one, and I've found the
> old behaviour annoying, and I've had to start a new gnus in a new
> emacs, after it has gotten confused after a suspend-resume.
How come? Automatic reconnection after the IMAP connection got closed
for whatever reason seems to work just fine with both the old and the
new nnimap. (I do remember issues with the old one and starttls that I
managed to work around by just using ssl instead of starttls.)
Is there another reason why Gnus would get confused when keeping
connections open while suspending?
While personally I still prefer the old behaviour, I don't have any
strong feelings about it either way. I'd be fine with writing a couple
more lines in my configuration to keep it the way I like if the new
behaviour is decided to be the preferred one. However, disconnecting on
suspend only to work around other unrelated bugs doesn't seem quite
right to me.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-09-27 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 9:50 Florian Ragwitz
2010-09-27 11:14 ` Steinar Bang
2010-09-27 12:22 ` Florian Ragwitz [this message]
2010-09-27 16:00 ` Steinar Bang
2010-09-27 16:34 ` Lars Magne Ingebrigtsen
2010-09-27 17:13 ` Steinar Bang
2010-09-27 22:55 ` Florian Ragwitz
2010-09-29 14:41 ` 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=8739sve5pw.fsf@tardis.home.perldition.org \
--to=rafl@debian.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).