From: Steven Tamm <steventamm@mac.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: OS X: C-g does not break out of infinite loop
Date: Sun, 18 Jul 2004 23:38:19 -0700 [thread overview]
Message-ID: <38F12CAA-D94E-11D8-A9B1-00039390AB82@mac.com> (raw)
In-Reply-To: <wlk6x0h6y5.wl@church.math.s.chiba-u.ac.jp>
On Jul 18, 2004, at 11:00 PM, YAMAMOTO Mitsuharu wrote:
> Hi,
> I thought I've explained that in the following message:
>
> http://lists.gnu.org/archive/html/emacs-devel/2004-04/msg01015.html
>
> Maybe your concern is another issue? Anyway, I can test with Mac OS X
> 10.1.5 if you give me an example that may cause some problems.
I missed that explanation during my prolonged illness. It makes sense,
given the rewrite of sys_select (Due to the "why didn't i think of
that" part of using ReceiveNextEvent with the timeout instead of
unnecessary selects).
So I guess the only thing I need to keep reverifying after each OS
release is the vfork problem.
>> However, I will check it in and let the 10.1 people complain because
>> the polling appears to work .
> Seems like the old patch is applied. It may cause a hang because of
> lack of BLOCK_INPUT/UNBLOCK_INPUT for ReceiveNextEvent, which I
> mentioned in
> http://lists.gnu.org/archive/html/emacs-devel/2004-05/msg00016.html
> Could you apply the attached patch over the current CVS?
Done. 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?
-Steven
next prev parent reply other threads:[~2004-07-19 6:38 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 [this message]
2004-07-19 7:13 ` YAMAMOTO Mitsuharu
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=38F12CAA-D94E-11D8-A9B1-00039390AB82@mac.com \
--to=steventamm@mac.com \
--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).