Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Freeze up on general news scan (g)
Date: Mon, 11 Nov 2013 10:40:15 -0500	[thread overview]
Message-ID: <87vbzzhrq8.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <87sivb8jxj.fsf@guybrush.luffy.cx>

On Tue, 05 Nov 2013 07:03:04 +0100 Vincent Bernat <bernat@luffy.cx> wrote: 

VB>  ❦  5 novembre 2013 03:59 CET, Eric Abrahamsen <eric@ericabrahamsen.net> :
EA> Thanks for this, at least it's good to know the state of affairs. It
EA> looks an elisp version of that sequence would be very simple: just call
EA> `gnus-server-close-all-servers', and then `gnus'.
>>> 
>>> It would be nice to add that to `gnus' as a user option (maybe a boolean
>>> `gnus-always-reopen-connections').  I worry, however, that adding it
>>> implicitly says we don't plan to solve the problem.
>> 
>> I wish I could be of more use, but network connectivity is foreign
>> territory to me. Where would you propose to add this reopen hook? How
>> would emacs/gnus know that, for instance, the computer had just resumed
>> from hibernation?

VB> I think that the proposition is to do this "unconditionally". So, when
VB> you resume your laptop, you type `M-x gnus` and you get the connections
VB> reopened.

Right.  The better way is to do it conditionally but it seems like a
hard problem.

VB> As to detect lose of connectivity, I think this is quite hard. If
VB> depending on D-Bus is OK, Gnus could listen to Network Manager's state
VB> (`StateChange` or `StateChanged`)

Yup, but NM is hardly universal and too many other things can break the
connection.  Lars had a big thread about it on emacs-devel.  I refresh
rarely so I wouldn't mind always reopening, but it does seem like giving
up on an interesting problem :)

Ted




  reply	other threads:[~2013-11-11 15:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 17:18 Harry Putnam
2012-01-03 23:17 ` Lars Magne Ingebrigtsen
2012-01-04 15:57   ` Harry Putnam
2012-01-06 14:33     ` Harry Putnam
2012-01-06 21:34       ` Lars Magne Ingebrigtsen
2013-10-06 17:54   ` Harry Putnam
2013-10-07  0:59     ` Eric Abrahamsen
2013-11-03 11:18       ` Ted Zlatanov
2013-11-04  2:15         ` Eric Abrahamsen
2013-11-04 16:47           ` Ted Zlatanov
2013-11-05  2:59             ` Eric Abrahamsen
2013-11-05  6:03               ` Vincent Bernat
2013-11-11 15:40                 ` Ted Zlatanov [this message]
2013-11-08 17:58               ` Harry Putnam

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=87vbzzhrq8.fsf@flea.lifelogs.com \
    --to=tzz@lifelogs.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).