From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ryan Johnson Newsgroups: gmane.emacs.devel Subject: Re: Best way to intercept terminal escape sequences? Date: Sat, 28 Aug 2010 09:54:23 +0200 Message-ID: <4C78C0AF.5040502@ece.cmu.edu> References: <20100827142724.E1DD712F@hazard.ece.cmu.edu> <4C77CF3C.6050406@ece.cmu.edu> <834oegm5c3.fsf@gnu.org> 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: dough.gmane.org 1282982084 30721 80.91.229.12 (28 Aug 2010 07:54:44 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 28 Aug 2010 07:54:44 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 28 09:54:42 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.69) (envelope-from ) id 1OpGFN-0007NX-BS for ged-emacs-devel@m.gmane.org; Sat, 28 Aug 2010 09:54:41 +0200 Original-Received: from localhost ([127.0.0.1]:35380 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OpGFM-0007EX-QO for ged-emacs-devel@m.gmane.org; Sat, 28 Aug 2010 03:54:40 -0400 Original-Received: from [140.186.70.92] (port=40356 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OpGFH-0007EO-Df for emacs-devel@gnu.org; Sat, 28 Aug 2010 03:54:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OpGFG-0006ms-7g for emacs-devel@gnu.org; Sat, 28 Aug 2010 03:54:35 -0400 Original-Received: from bache.ece.cmu.edu ([128.2.129.23]:54919) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OpGFF-0006mU-0x; Sat, 28 Aug 2010 03:54:33 -0400 Original-Received: from [192.168.0.2] (145-122.76-83.cust.bluewin.ch [83.76.122.145]) by bache.ece.cmu.edu (Postfix) with ESMTP id 5E95ECE; Sat, 28 Aug 2010 03:54:31 -0400 (EDT) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Solaris 9 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:129332 Archived-At: On 8/28/2010 1:54 AM, Stefan Monnier wrote: >> I think the only way that is easier and cleaner would be if Emacs >> could read the mouse input from a separate file descriptor. We could > Note that under older Emacsen, read-event did not obey the > keyboard-coding-system at all: it only applied to read-key-sequence. > So maybe we should simply change read-event not to try and decoding > keyboard input. That might make sense... the caller could always apply the coding system manually before dumping things back in the unread-command-events queue. Who currently uses read-* that might be affected? xt-mouse.el would love it, mouse.el certainly won't care, and other xterm processing will be indifferent. BTW, I've been playing with read-key and it's perfect for making mouse.el and xt-mouse.el play nice together! I'm a tad unclear on the difference between read-key and read-key-sequence, though, other than the latter letting you supply a minibuffer prompt. Ryan