Gnus development mailing list
 help / color / mirror / Atom feed
From: Leo <sdl.web@gmail.com>
Cc: ding@gnus.org
Subject: Re: gnus makes emacs lose response
Date: Tue, 26 Sep 2006 18:26:24 +0100	[thread overview]
Message-ID: <m2vena7d4v.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: <8764fe4fb9.fsf@stupidchicken.com>

On Sat, 09/23/2006 19:18 +0100, Chong Yidong wrote:

> After some further communication with Leon, I think I know the
> problem: accept-process-output is called by the timer function
> `gnus-demon' (which is a valid but IIUC not commonly-used component of
> Gnus).  However, as documented in the Lisp Reference manual:
>
>    Emacs binds `inhibit-quit' to `t' before calling the timer
>    function, because quitting out of many timer functions can leave
>    things in an inconsistent state.  This is normally unproblematical
>    because most timer functions don't do a lot of work.  Indeed, for a
>    timer to call a function that takes substantial time to run is
>    likely to be annoying.
>
> The result in this case is that this accept-process-output can't be
> interrupted, and Emacs can hang if the process doesn't reply (e.g., if
> the connection dies).
>
> I'm not sure what the best way to handle this is.  Anyone?

The ChangeLog says it's fixed. But I can't see the actually
fix. gnus-demon.el has not been changed for 7 month.

-- 
Leo

  parent reply	other threads:[~2006-09-26 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23 18:18 Chong Yidong
2006-09-23 23:42 ` Luc Teirlinck
2006-09-26 17:26 ` Leo [this message]
2006-09-26 18:08   ` Chong Yidong
2006-09-26 19:20     ` Leo
  -- strict thread matches above, loose matches on Subject: below --
2006-04-06 20:41 Dave Love
2006-03-29 23:02 [sdl.web@gmail.com: gnus makes emacs lose response] Richard Stallman
2006-04-05 18:30 ` Dave Love
2006-04-06 15:37   ` Richard Stallman
2006-04-06 16:43     ` gnus makes emacs lose response Reiner Steib

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=m2vena7d4v.fsf@sl392.st-edmunds.cam.ac.uk \
    --to=sdl.web@gmail.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).