emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Pretest next week


From: Adrian Robert
Subject: Re: Pretest next week
Date: Tue, 27 Jan 2009 01:08:00 +0200


On Jan 27, 2009, at 12:07 AM, Chong Yidong wrote:

Adrian Robert <address@hidden> writes:

3) Make sure some kind of interrupt mechanism is in place to pick up
ctrl-g events when emacs core is busy processing and does not
itself make passes through the NS code event loop (colored spinning
disk shown in gui).

Here, the issue is that the SIGIO handler is never called, despite
being registered.  It might be overridden by Cocoa in some way,
though I haven't been able to fully confirm this.

Have you checked whether the SIGIO handler is registered in the first
place?  Also, have you confirmed that the handling function is indeed
never called (as opposed to a bug that makes it do nothing)?

Yes, signal() IS called with SIGIO, input_available_signal(), and the latter is never called (according to an fprintf which works fine running under X). I also tried calling signal() at various later times, in case the handler gets replaced.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]