unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: OS X: C-g does not break out of infinite loop
Date: Mon, 19 Jul 2004 16:13:51 +0900	[thread overview]
Message-ID: <wlekn8h3kg.wl@church.math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <38F12CAA-D94E-11D8-A9B1-00039390AB82@mac.com>

>>>>> On Sun, 18 Jul 2004 23:38:19 -0700, Steven Tamm <steventamm@mac.com> said:

> I have noticed that responding to blocked subcommands still takes a
> second to respond, which seems odd since it should be 200ms.  Have
> you noticed this as well?

That is what I intended, and normal for the systems where SIGIO can't
be used for notification of input events.  The documentation of
`polling-period' says:

  *Interval between polling for input during Lisp execution.
  The reason for polling is to make C-g work to stop a running program.
  Polling is needed only when using X windows and SIGIO does not work.
  Polling is automatically disabled in all other cases.

During Lisp or synchronous subprocess execution, window events
(including keyboard ones) are inspected every `polling-period' (2 by
default) seconds.  The timeout `200ms' (I think you meant 20ms =
20000ns in mac.c) is just for multiplexing the inspection of window
events by ReceiveNextEvent and that of process I/O by select.

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp

      reply	other threads:[~2004-07-19  7:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 16:54 OS X: C-g does not break out of infinite loop John Owens
2004-07-15 13:17 ` Richard Stallman
2004-07-15 13:57   ` YAMAMOTO Mitsuharu
2004-07-15 20:25     ` John Owens
     [not found]     ` <202E9468-D93E-11D8-A9B1-00039390AB82@mac.com>
     [not found]       ` <wlk6x0h6y5.wl@church.math.s.chiba-u.ac.jp>
2004-07-19  6:38         ` Steven Tamm
2004-07-19  7:13           ` YAMAMOTO Mitsuharu [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wlekn8h3kg.wl@church.math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).