From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Bikeshedding go! Why is unbound? Date: Fri, 14 Jan 2011 01:21:07 +0100 Message-ID: References: <87sjx7z7w4.fsf@telefonica.net> <83pqsbmf6j.fsf@gnu.org> <87k4ijz07h.fsf@telefonica.net> <2460D97DEA4047B3B9DF92C4A80981EF@us.oracle.com> <57BF13882D6E494286547F293FE9D03B@us.oracle.com> <87lj2pfo81.fsf@wanadoo.es> <87tyhcel25.fsf@wanadoo.es> <4D2F94EF.4010302@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: dough.gmane.org 1294964524 24522 80.91.229.12 (14 Jan 2011 00:22:04 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 14 Jan 2011 00:22:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 14 01:21:57 2011 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.69) (envelope-from ) id 1PdXQH-0005WZ-5E for ged-emacs-devel@m.gmane.org; Fri, 14 Jan 2011 01:21:45 +0100 Original-Received: from localhost ([127.0.0.1]:49286 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PdXQG-0004sj-IL for ged-emacs-devel@m.gmane.org; Thu, 13 Jan 2011 19:21:44 -0500 Original-Received: from [140.186.70.92] (port=35003 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PdXQ2-0004kE-5u for emacs-devel@gnu.org; Thu, 13 Jan 2011 19:21:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PdXQ1-0007VS-4e for emacs-devel@gnu.org; Thu, 13 Jan 2011 19:21:30 -0500 Original-Received: from mail-ew0-f41.google.com ([209.85.215.41]:40668) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PdXQ0-0007V3-Rb; Thu, 13 Jan 2011 19:21:29 -0500 Original-Received: by ewy27 with SMTP id 27so1150681ewy.0 for ; Thu, 13 Jan 2011 16:21:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=qbGZiBMdElXfRRBjjnKRBRCYMQex9Rf+Q858wVtbJyY=; b=FdmKekW5WVFLEDFhEbPf94i5Z/+SacjjW6sVv4IS3po8SZ72rOtBOJbRVC4N116fZg oycIdc0/A1LDxglXloBfP75wNtUvWQ6g33k3nryCIfQzpNgm6hq4ODMcBzVMGxFBYhcV Fipvrl9Ji979y05bFvoNMSej7MOBoGcW6SE/w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=Yx3Jl9PyDmxdhzKqlngsLHJcyBk+BaD+g6eVU7W1sPe015pPe+MNhVS3IEvA0Ih7Ot urs59rtC+lH0pmlHirDlAY6mLeE9v/RDPZGPSYT9qYxDjZIdkZ8sPfqE4YeTOZxLIA3t uiDIZNSLpwjmvkcbp1O24vPmz4DwlblwLgxek= Original-Received: by 10.213.10.75 with SMTP id o11mr225267ebo.71.1294964487587; Thu, 13 Jan 2011 16:21:27 -0800 (PST) Original-Received: by 10.213.20.148 with HTTP; Thu, 13 Jan 2011 16:21:07 -0800 (PST) In-Reply-To: <4D2F94EF.4010302@gnu.org> X-detected-operating-system: by eggs.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:134509 Archived-At: On Fri, Jan 14, 2011 at 1:12 AM, Jason Rumney wrote: > On 14/01/2011 06:00, Lennart Borgman wrote: >> >> To delegate Alt-F4 to Windows standard routine we have to catch it in >> the message loop. I can't remember how it shows up in the message >> loop. Does it come in one peace (i.e. Alt+F4) or in a sequence (i.e. >> Alt and then F4)? >> > > It comes in peace, as one piece. ;-) I thought I had left that habit of mispelling... - Some day I will learn reading. > More specifically the events should come as the following sequence: > > Alt Down > F4 Down with Alt modifier set > F4 Up with Alt modifier set > Alt Up > > If the second event is passed to Windows to handle, I suspect the third > event may not arrive to Emacs. Is then all we have to do pass the second event to Windows?