Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Love <fx@gnu.org>
Cc: ding@gnus.org
Subject: Re: [sdl.web@gmail.com: gnus makes emacs lose response]
Date: Wed, 05 Apr 2006 19:30:21 +0100	[thread overview]
Message-ID: <rzqzmizri2q.fsf@loveshack.ukfsn.org> (raw)
In-Reply-To: <E1FOjgG-0007hR-OD@fencepost.gnu.org> (Richard Stallman's message of "Wed, 29 Mar 2006 18:02:24 -0500")

Richard Stallman <rms@gnu.org> writes:

> Would someone please take a look?
>
> ------- Start of forwarded message -------
> To: emacs-pretest-bug@gnu.org
> From: Leon <sdl.web@gmail.com>
> Date: Wed, 29 Mar 2006 03:44:12 +0100
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Subject: gnus makes emacs lose response
> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
> 	version=3.0.4
>
> Dear all,
>
> If I am using gnus and disconnect the network cable, after a while
> emacs will lose response. C-g won't work. I have to `killall emacs'. I
> think this is due to demon trying to fetch news/emails.

This is a longstanding problem with background processes.  I sent a
test case maybe two years ago, but as far as I know it never got fixed
and I couldn't follow the process code to fix it confidently.  I can't
find the test case, but I seem to remember it involved the timeout on
`accept-process-output' not being obeyed.

If you're on a tty, C-g in this state stops Emacs and gives you the
`abort or auto-save' question.  Non-keyboard input is still processed,
so that you can get out of it by invoking `top-level' with the
`gnudoit' program or having bound that to a user signal and sending
the signal.



  reply	other threads:[~2006-04-05 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 23:02 Richard Stallman
2006-04-05 18:30 ` Dave Love [this message]
2006-04-06 15:37   ` Richard Stallman
2006-04-06 16:43     ` gnus makes emacs lose response Reiner Steib
2006-04-06 18:52 [sdl.web@gmail.com: gnus makes emacs lose response] Dave Love
2006-04-07  2:19 ` Richard Stallman

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=rzqzmizri2q.fsf@loveshack.ukfsn.org \
    --to=fx@gnu.org \
    --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).