[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Reviving Gnus after suspend/hibernation
From: |
Eli Zaretskii |
Subject: |
Re: Reviving Gnus after suspend/hibernation |
Date: |
Thu, 27 Oct 2011 20:14:58 +0200 |
> From: Ted Zlatanov <address@hidden>
> Date: Thu, 27 Oct 2011 13:41:43 -0400
> Cc: address@hidden
>
> Asking emacs-devel since the Gnus list didn't have any answers:
>
> On Mon, 24 Oct 2011 09:23:09 -0400 Ted Zlatanov <address@hidden> wrote:
>
> TZ> On Tue, 18 Oct 2011 18:39:11 +0200 address@hidden (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.
What exactly is the question?
- Re: Reviving Gnus after suspend/hibernation, Ted Zlatanov, 2011/10/27
- Re: Reviving Gnus after suspend/hibernation,
Eli Zaretskii <=
- Re: Reviving Gnus after suspend/hibernation, joakim, 2011/10/27
- Re: Reviving Gnus after suspend/hibernation, Stefan Monnier, 2011/10/27
- Re: Reviving Gnus after suspend/hibernation, Ted Zlatanov, 2011/10/27
- Re: Reviving Gnus after suspend/hibernation, Stefan Monnier, 2011/10/27
- Re: Reviving Gnus after suspend/hibernation, Ted Zlatanov, 2011/10/28