From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Jan D." Newsgroups: gmane.emacs.devel Subject: Re: Emacs 23 Mac port Date: Wed, 13 Jan 2010 08:43:04 +0100 Message-ID: <4B4D7988.90402@swipnet.se> References: <2282B3B4-D844-4E26-BB94-9F79EEA2E847@gmail.com> <4B4C2FD7.8070406@swipnet.se> 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 1263368606 14798 80.91.229.12 (13 Jan 2010 07:43:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 13 Jan 2010 07:43:26 +0000 (UTC) Cc: emacs-devel@gnu.org, Stefan Monnier , Leo To: YAMAMOTO Mitsuharu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 13 08:43:18 2010 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 1NUxsr-0005ci-Pr for ged-emacs-devel@m.gmane.org; Wed, 13 Jan 2010 08:43:18 +0100 Original-Received: from localhost ([127.0.0.1]:58516 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NUxss-0001ZB-Dz for ged-emacs-devel@m.gmane.org; Wed, 13 Jan 2010 02:43:18 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NUxsm-0001Ws-TJ for emacs-devel@gnu.org; Wed, 13 Jan 2010 02:43:12 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NUxsi-0001Qu-17 for emacs-devel@gnu.org; Wed, 13 Jan 2010 02:43:12 -0500 Original-Received: from [199.232.76.173] (port=57799 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NUxsh-0001Qk-SK for emacs-devel@gnu.org; Wed, 13 Jan 2010 02:43:07 -0500 Original-Received: from mx20.gnu.org ([199.232.41.8]:48051) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NUxsh-0004Rk-CV for emacs-devel@gnu.org; Wed, 13 Jan 2010 02:43:07 -0500 Original-Received: from proxy3.bredband.net ([195.54.101.73]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NUxsg-0007gh-OJ for emacs-devel@gnu.org; Wed, 13 Jan 2010 02:43:07 -0500 Original-Received: from ipb2.telenor.se (195.54.127.165) by proxy3.bredband.net (7.3.140.3) id 4AD3E1BA02445164 for emacs-devel@gnu.org; Wed, 13 Jan 2010 08:43:05 +0100 X-SMTPAUTH-B2: X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnxVAI8ITUtV4S1uPGdsb2JhbACBRIZvky0BAQEBN7kMhDAEjTw X-IronPort-AV: E=Sophos;i="4.49,267,1262559600"; d="scan'208";a="26192948" Original-Received: from c-6e2de155.25-1-64736c10.cust.bredbandsbolaget.se (HELO coolsville.localdomain) ([85.225.45.110]) by ipb2.telenor.se with ESMTP; 13 Jan 2010 08:43:05 +0100 Original-Received: from [10.225.40.84] (unknown [193.45.43.33]) by coolsville.localdomain (Postfix) with ESMTPSA id 172087FA01A; Wed, 13 Jan 2010 08:43:05 +0100 (CET) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 In-Reply-To: X-detected-operating-system: by mx20.gnu.org: Genre and OS details not recognized. X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:119902 Archived-At: On 2010-01-13 00:35, YAMAMOTO Mitsuharu wrote: >>>>>> On Tue, 12 Jan 2010 09:15:11 -0500, Stefan Monnier said: > >>> Thanks. But then a special event such as SIGUSR1 cancels an >>> incomplete key sequence being typed. How about doing this only >>> when the current buffer is changed by the special event? > >> IIRC the general approach to these kinds of problems in >> read-key-sequence is to only recompute the initial state if the >> current key-sequence is still empty. I.e. rather than check whether >> the special event has changed current buffer, we would instead check >> whether the keybuf is still empty. > > Well, at least, it seems to be much cleaner for read_char just to > return a special code (instead of -2) indicating a command is executed > via special event map, and let the caller determine what to do for > that case. The problem is read_char is called from many places. Jan D.