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: Wed, 28 Jan 2009 14:19:55 +0200 Message-ID: <3765D6BE-634B-4D1E-AF8B-7822957F88C7@gmail.com> References: <87y6x4ue2u.fsf@cyd.mit.edu> <87mydjv4bd.fsf@cyd.mit.edu> <08054F25-1F90-4795-9FFE-01363F6900CE@gmail.com> <497E6D32.9000707@gnu.org> <87tz7kawln.fsf@cyd.mit.edu> <4980268C.9020104@gnu.org> 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 1233145241 13911 80.91.229.12 (28 Jan 2009 12:20:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 28 Jan 2009 12:20:41 +0000 (UTC) Cc: Chong Yidong , emacs-devel@gnu.org To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 28 13:21:54 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 1LS9QI-0006UY-Sf for ged-emacs-devel@m.gmane.org; Wed, 28 Jan 2009 13:21:39 +0100 Original-Received: from localhost ([127.0.0.1]:48902 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LS9P0-0007Ro-Ol for ged-emacs-devel@m.gmane.org; Wed, 28 Jan 2009 07:20:18 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LS9Ob-00079o-Dc for emacs-devel@gnu.org; Wed, 28 Jan 2009 07:19:53 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LS9Oa-00078d-JY for emacs-devel@gnu.org; Wed, 28 Jan 2009 07:19:52 -0500 Original-Received: from [199.232.76.173] (port=37849 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LS9Oa-00078N-7I for emacs-devel@gnu.org; Wed, 28 Jan 2009 07:19:52 -0500 Original-Received: from fg-out-1718.google.com ([72.14.220.152]:48063) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LS9OW-0003bV-Fm; Wed, 28 Jan 2009 07:19:48 -0500 Original-Received: by fg-out-1718.google.com with SMTP id e12so565562fga.30 for ; Wed, 28 Jan 2009 04:19:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=ntYjdqGJcl1W36K8st1m6sVrT4z4qgpWzLRQLhNM2jc=; b=TqjE3SJc54TG9vlVI2k3vURrMtzFsv6d3KMREJ9UZIzUdUkPZDX7nowV6nuajWBmjk qnPxLIRRR4bY1SWe+W/70iZD+fFvaCljb5DkH7RZKPyj6qkfgjhJmX4rW+ugeBf3BoZW gIZ5l+YmkIGh3Uwi1/IiLClLiq/Pmrji1nFg8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=BPxkKi4f8LoXu0POFH6snjs8lMll/fQKqvyO1tLSCe0yh6PjFSMrfkO1ZR58DSO7CU VNgmm0M6QfbiPLtUKWfM4Wvxir56E0ThV4Nk0P/YkJaVkcB/J4lQ94g6EldqQIjFXGaP HCC5EcjjDsBvwsrlkwSsfJc2HIsaBd2rZf294= Original-Received: by 10.223.124.137 with SMTP id u9mr771802far.61.1233145187119; Wed, 28 Jan 2009 04:19:47 -0800 (PST) Original-Received: from ?192.168.1.101? (i036133.gprs.dnafinland.fi [87.95.36.133]) by mx.google.com with ESMTPS id 7sm1366197eyg.42.2009.01.28.04.19.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 28 Jan 2009 04:19:46 -0800 (PST) In-Reply-To: <4980268C.9020104@gnu.org> 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:108326 Archived-At: On Jan 28, 2009, at 11:34 AM, Jason Rumney wrote: > Chong Yidong wrote: >> Adrian Robert writes: >> >> >>> What is the entry point for detecting the Ctrl-G (or any other user >>> keyboard input), when a tight loop is running, such as (while t t)? >>> Is the SIGIO signal handler used, or is W32 itself asynchronously >>> calling something in w32fns.c or w32term.c on a second thread? >>> >> >> I think this is done in the SIGIO signal handler (at least, >> according to >> the comment for w32_read_socket in w32fns.c). Jason, could you >> confirm >> this? >> > > W32 does not have a SIGIO signal handler, so that comment is > probably a copy and paste error. On Windows, a second thread is > listening for window system messages. w32_read_socket is the Lisp > thread's message handler, C-g detection is done in > post_character_message (w32fns.c) which is the point where the > input message is posted from the window system message handling > thread to the lisp thread. This could probably be done under NS as well. There might be issues with one or the other thread needing to be the "primary" one, and some degree of rearchitecting would be needed, using the W32 port as a guide. So, it might be simpler if there's any way to get the conventional keyboard.c timer-driven input polling done through the QUIT macro under NS.