From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Emacs 23 Mac port Date: Tue, 12 Jan 2010 09:15:11 -0500 Message-ID: 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=us-ascii X-Trace: ger.gmane.org 1263305735 16188 80.91.229.12 (12 Jan 2010 14:15:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 Jan 2010 14:15:35 +0000 (UTC) Cc: Jan =?iso-8859-1?Q?Dj=E4rv?= , Leo , emacs-devel@gnu.org To: YAMAMOTO Mitsuharu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 12 15:15:27 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 1NUhWn-0006Q1-UF for ged-emacs-devel@m.gmane.org; Tue, 12 Jan 2010 15:15:26 +0100 Original-Received: from localhost ([127.0.0.1]:41500 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NUhWm-00078l-6I for ged-emacs-devel@m.gmane.org; Tue, 12 Jan 2010 09:15:24 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NUhWf-00078C-PV for emacs-devel@gnu.org; Tue, 12 Jan 2010 09:15:17 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NUhWb-00076J-2D for emacs-devel@gnu.org; Tue, 12 Jan 2010 09:15:17 -0500 Original-Received: from [199.232.76.173] (port=54292 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NUhWa-00076E-Ui for emacs-devel@gnu.org; Tue, 12 Jan 2010 09:15:12 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:3271 helo=ironport2-out.pppoe.ca) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NUhWa-0000T0-Ok for emacs-devel@gnu.org; Tue, 12 Jan 2010 09:15:12 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEAD8STEvO+KPG/2dsb2JhbACBRdQ0hDAEii+DCw X-IronPort-AV: E=Sophos;i="4.49,262,1262581200"; d="scan'208";a="53582916" Original-Received: from 206-248-163-198.dsl.teksavvy.com (HELO ceviche.home) ([206.248.163.198]) by ironport2-out.pppoe.ca with ESMTP; 12 Jan 2010 09:15:12 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id D26EDB4649; Tue, 12 Jan 2010 09:15:11 -0500 (EST) In-Reply-To: (YAMAMOTO Mitsuharu's message of "Tue, 12 Jan 2010 18:03:40 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.91 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:119871 Archived-At: > 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. Stefan