From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel Subject: Re: Pretest next week Date: Wed, 28 Jan 2009 17:34:04 +0800 Message-ID: <4980268C.9020104@gnu.org> 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> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1233135297 15795 80.91.229.12 (28 Jan 2009 09:34:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 28 Jan 2009 09:34:57 +0000 (UTC) Cc: Adrian Robert , emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 28 10:36:09 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 1LS6q7-0005OT-Re for ged-emacs-devel@m.gmane.org; Wed, 28 Jan 2009 10:36:08 +0100 Original-Received: from localhost ([127.0.0.1]:51732 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LS6op-0001Cv-QZ for ged-emacs-devel@m.gmane.org; Wed, 28 Jan 2009 04:34:47 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LS6ok-0001Cq-GS for emacs-devel@gnu.org; Wed, 28 Jan 2009 04:34:42 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LS6oi-0001Ce-HH for emacs-devel@gnu.org; Wed, 28 Jan 2009 04:34:41 -0500 Original-Received: from [199.232.76.173] (port=45245 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LS6oi-0001Cb-9Z for emacs-devel@gnu.org; Wed, 28 Jan 2009 04:34:40 -0500 Original-Received: from wf-out-1314.google.com ([209.85.200.173]:28395) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LS6oh-0007Ju-PK for emacs-devel@gnu.org; Wed, 28 Jan 2009 04:34:40 -0500 Original-Received: by wf-out-1314.google.com with SMTP id 28so6857213wfc.24 for ; Wed, 28 Jan 2009 01:34:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=SvwqD4TDgDx4k6Znw+fV2BvzAOsM+lzoq75xzl+vA1U=; b=GczXwPTQCw2XuhAVIrjbzN95qPlYQXmkmOpCfYFBRoQqouPszwC76hIk5JiUubJype eG7gBlEjxZLo9VykBbDPswYMSvqgrZKUXpWAnki9buSO5vPZ+mYr0GUWZxYn5hIM44Gs iPOTaolk1oUSxn1LUrY8gcKvEBknDYXKVllsE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=tIYITAxdfZRTyUcVOrFau72NHGZWAsDv1sal64Tle53AOgauD7tjQsBqOkkwZ4AEOD 596OOCHMa+S/QElT4czeaN75sGXxae4t5e1VfKUUX5DlMbcPLuYo8sgwciwYNKgk5IU8 h4+siahJ2ZGQ3ltYTqYyaCG9p+SVWb6Zz5jmM= Original-Received: by 10.143.45.14 with SMTP id x14mr274431wfj.165.1233135277956; Wed, 28 Jan 2009 01:34:37 -0800 (PST) Original-Received: from ?192.168.249.26? ([118.101.26.137]) by mx.google.com with ESMTPS id 24sm1715608wff.57.2009.01.28.01.34.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 28 Jan 2009 01:34:37 -0800 (PST) User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) In-Reply-To: <87tz7kawln.fsf@cyd.mit.edu> 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:108325 Archived-At: 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.