From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Adrian Robert Newsgroups: gmane.emacs.devel Subject: Re: Pretest next week Date: Tue, 27 Jan 2009 01:08:00 +0200 Message-ID: <63641E4C-FA81-499C-9EC3-6D1F2778D2D6@gmail.com> References: <87y6x4ue2u.fsf@cyd.mit.edu> <87mydjv4bd.fsf@cyd.mit.edu> <08054F25-1F90-4795-9FFE-01363F6900CE@gmail.com> <874ozlhgc4.fsf@cyd.mit.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1233013169 20002 80.91.229.12 (26 Jan 2009 23:39:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 26 Jan 2009 23:39:29 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 27 00:40:42 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LRb4L-0004bQ-Tm for ged-emacs-devel@m.gmane.org; Tue, 27 Jan 2009 00:40:42 +0100 Original-Received: from localhost ([127.0.0.1]:46118 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LRb34-0006mD-14 for ged-emacs-devel@m.gmane.org; Mon, 26 Jan 2009 18:39:22 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LRaZ2-0003c8-9c for emacs-devel@gnu.org; Mon, 26 Jan 2009 18:08:20 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LRaZ1-0003bt-Ju for emacs-devel@gnu.org; Mon, 26 Jan 2009 18:08:19 -0500 Original-Received: from [199.232.76.173] (port=45275 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LRaZ1-0003bq-Et for emacs-devel@gnu.org; Mon, 26 Jan 2009 18:08:19 -0500 Original-Received: from mail-ew0-f20.google.com ([209.85.219.20]:53394) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LRaZ0-00054b-W3 for emacs-devel@gnu.org; Mon, 26 Jan 2009 18:08:19 -0500 Original-Received: by ewy13 with SMTP id 13so1286843ewy.18 for ; Mon, 26 Jan 2009 15:08:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version:in-reply-to :references:content-type:message-id:content-transfer-encoding:from :subject:date:to:x-mailer; bh=NuyOQaFB6aZOTMBjEKcwKobxjKpJnPWpgLoPyZyXNzU=; b=DToflSj489GEH/v6QlQ2+p1+Iu2vYPLq+kw3TPrP9hLfPJMVJ7DRe8+uOt4ua0+cdY FdU3v1MJ0NuSOScln+d1EhiXA0Xl1ceDssB0h/lNZArE8qlmg3cJT+hpYseAIYM5BDKJ IyW2rc/u2OhfURb1a+2F3zOGztvEnoW4uYqVY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id :content-transfer-encoding:from:subject:date:to:x-mailer; b=OWulfvfXdk0sdQCm9s59bEwBdHmwVeHukpeCYJhGHUHCXbmlQrBIDuJcmB+wRVwts6 YzigF6viGEB+prk9eyAwr4L2NTPWpFKn+pGxfjzyhWLPm6T8d/tmJCO52E0W2Aq3a7bp VTxTT+bH/VnwF7XTOnvas0xd6Jl/eQe8TvKuM= Original-Received: by 10.210.112.1 with SMTP id k1mr298577ebc.167.1233011297558; Mon, 26 Jan 2009 15:08:17 -0800 (PST) Original-Received: from ?192.168.1.101? (i008223.gprs.dnafinland.fi [87.95.8.223]) by mx.google.com with ESMTPS id 10sm744298eyz.59.2009.01.26.15.08.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 26 Jan 2009 15:08:16 -0800 (PST) In-Reply-To: <874ozlhgc4.fsf@cyd.mit.edu> X-Mailer: Apple Mail (2.753.1) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:108270 Archived-At: On Jan 27, 2009, at 12:07 AM, Chong Yidong wrote: > Adrian Robert 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.