From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Dealing with hanging IMAP connections
Date: Mon, 30 Nov 2009 09:53:58 +0100 [thread overview]
Message-ID: <yb0ws18e6l5.fsf@osl2u223.oslo2.fast.no> (raw)
In-Reply-To: <87einq6us0.fsf@myles.home.wjsullivan.net>
>>>>> John Sullivan <john@wjsullivan.net>:
> In these situations, you might also try M-x list-processes, then
> (kill-process "imap") or "imap<1>" etc. That's what I often have to do
> when I change networks.
Changing networks is usually ok, at least if you remember to unplug gnus
before sleeping the machine. But changing NIC (e.g. from a wired NIC to
a WLAN NIC, or a 3G connection), can confuse Gnus so badly, you're
better off starting a new Gnus in a new emacs...
next prev parent reply other threads:[~2009-11-30 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 21:18 David Engster
2009-11-22 22:48 ` John Sullivan
2009-11-23 7:59 ` Frank Schmitt
2009-11-30 10:30 ` Bojan Nikolic
2009-11-23 15:50 ` David Engster
2009-11-29 1:06 ` Ludovic Courtès
2009-11-30 8:53 ` Steinar Bang [this message]
2009-11-22 22:58 ` Reiner Steib
2009-11-23 3:02 ` Stefan Monnier
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=yb0ws18e6l5.fsf@osl2u223.oslo2.fast.no \
--to=sb@dod.no \
--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).