|
From: | Ryan Johnson |
Subject: | Re: Best way to intercept terminal escape sequences? |
Date: | Sat, 28 Aug 2010 09:54:23 +0200 |
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 |
On 8/28/2010 1:54 AM, Stefan Monnier wrote:
That might make sense... the caller could always apply the coding system manually before dumping things back in the unread-command-events queue.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 couldNote 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.
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
[Prev in Thread] | Current Thread | [Next in Thread] |