From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: Reviving Gnus after suspend/hibernation
Date: Fri, 28 Oct 2011 18:27:02 +0200 [thread overview]
Message-ID: <uw39edaxpl.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87obx2e17x.fsf@gmail.com>
coroa@online.de (Jonas Hörsch) writes:
> On Thu, Oct 27 2011, Ted Zlatanov wrote:
>
>> Asking emacs-devel since the Gnus list didn't have any answers:
>>
>> On Mon, 24 Oct 2011 09:23:09 -0400 Ted Zlatanov <tzz@lifelogs.com> wrote:
>>
>> TZ> On Tue, 18 Oct 2011 18:39:11 +0200 ludo@gnu.org (Ludovic Courtès) wrote:
>> LC> When Gnus is left plugged or has non-agentized nnimap groups, recovering
>> LC> from suspend-to-RAM or hibernation has always been a problem for me:
>> LC> sometimes Emacs is frozen upon resume, trying to get data from some IMAP
>> LC> stream.
>> ...
>> TZ> (Assuming modern GNU/Linux system is the main focus based on your
>> TZ> commands)
>>
>> TZ> Is there a D-BUS signal for this, and can Emacs catch it? If so I could
>> TZ> try to close the open connections in that handler.
>>
>> TZ> What happens on a W32 system?
>>
>> Any help is appreciated. I don't know anything about these system events.
>>
>> Thanks
>> Ted
>
> I'm not sure about catching a suspend event, that probably is based on
> who is suspending anyway (Is it a DBUS-using power manager, like KDE's
> powerdevil or the gnome-power-manager?).
>
> But if the network interfaces are managed by NetworkManager, you can at
> least hook into connect/disconnect signals. There is some working
> implementation on the EmacsWiki:
>
> http://www.emacswiki.org/emacs/GnusNetworkManager
>
NetworkManager is uninstalled by many of us because it can be buggy, is
poor at handling VPNs and "does its own thing" rather than respect the
interfaces file. So if this could be done at a point common to both NM
*and* manual interfaces/wpa__supplicant handling that would be better.
next prev parent reply other threads:[~2011-10-28 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 16:39 Ludovic Courtès
2011-10-18 17:15 ` Richard Riley
2011-10-18 18:00 ` Tassilo Horn
2011-10-18 19:14 ` Dave Abrahams
2011-10-19 6:20 ` Tassilo Horn
2011-10-21 15:31 ` Ludovic Courtès
2011-10-21 16:59 ` Steinar Bang
2011-10-21 23:58 ` Dave Abrahams
2011-10-22 9:07 ` Steinar Bang
2011-10-22 20:29 ` Dave Abrahams
2011-10-18 19:13 ` Dave Abrahams
2011-10-24 13:23 ` Ted Zlatanov
2011-10-27 17:41 ` Ted Zlatanov
2011-10-27 18:30 ` Jonas Hörsch
2011-10-28 16:27 ` Richard Riley [this message]
2011-10-29 19:07 ` Antoine Levitt
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=uw39edaxpl.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.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).