From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: gnus makes emacs lose response
Date: Sat, 23 Sep 2006 18:42:07 -0500 (CDT) [thread overview]
Message-ID: <200609232342.k8NNg7pL007121@jane.dms.auburn.edu> (raw)
In-Reply-To: <8764fe4fb9.fsf@stupidchicken.com> (message from Chong Yidong on Sat, 23 Sep 2006 14:18:34 -0400)
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?
I have no time to look at the actual code, but is there any reason why
the routine way to handle this problem, namely using `with-local-quit'
(see (elisp)Quitting) around the problematic code (in this case
probably the call to accept-process-output) does not work in this case?
Sincerely,
Luc.
next prev parent reply other threads:[~2006-09-23 23:42 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 [this message]
2006-09-26 17:26 ` Leo
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=200609232342.k8NNg7pL007121@jane.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).