From: joakim@verona.se
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Blocking call to accept-process-output with quit inhibited!! [11 times]
Date: Tue, 07 Sep 2010 09:08:26 +0200 [thread overview]
Message-ID: <m3tym2f2tx.fsf@verona.se> (raw)
In-Reply-To: <jwv62yieeqa.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 06 Sep 2010 23:41:05 +0200")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> In Emacs 24, I get this message the first time I enter a Gnus group.
>> What does it mean, and what can I do to make it go away?
>
> It means just that: accept-process-output is called in a way that can
> block (e.g. because some remote host doesn't respond) wit inhibit0quit
> set to a non-nil value, which means that Emacs may end up frozen (with
> no way to wake it up) for as long as the remote machine decides not
> to answer.
>
> IOW, maybe there should be a (with-local-quit ...) somewhere so that the
> user can C-g out of such a state (or the call should have a timeout, or
> inhibit-quit should not be set, ...).
I get bitten by this quite a lot, since I'm often on a flaky 3g
line. When the link goes down, and some Emacs socket is still up, Emacs
freezes. This is quite annoying.
I suppose that the hard blocking is there to prevent data loss or
whatever, but having to kill -9 Emacs results in worse dataloss.
>
>
> Stefan
--
Joakim Verona
next prev parent reply other threads:[~2010-09-07 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m37hiya7na.fsf@quimbies.gnus.org>
2010-09-06 21:41 ` Stefan Monnier
2010-09-06 21:48 ` Lars Magne Ingebrigtsen
2010-09-07 7:08 ` joakim [this message]
2010-09-07 10:38 ` Stefan Monnier
2010-09-07 11:11 ` joakim
2010-09-07 11:53 ` Lars Magne Ingebrigtsen
2010-09-08 8:10 ` Stefan Monnier
2010-09-07 18:33 ` Tom Tromey
2010-09-08 8:12 ` Stefan Monnier
2010-09-07 11:54 ` Lars Magne Ingebrigtsen
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=m3tym2f2tx.fsf@verona.se \
--to=joakim@verona.se \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).