Re: Fwd: Mouse reporting and new standards

On Mon, Jan 23, 2012 at 09:21:50AM +0100, Egmont Koblinger wrote:
> On Mon, Jan 23, 2012 at 01:26, Thomas Dickey <dickey@his.com> wrote:
>
> >
> > I'd assume that one would start by doing a
> >
> > (define-key input-decode-map "\e[<"
> > 'xterm-extended-mouse-translate))
> >
> > ...along with a suitable new function. It's been a while since I
> > programmed in lisp, but it's usually readable. Aside from
> > cut/paste/massage
> > of text already in the file, there's not much to lookup.
> >
>
> It's clear as long as mouse is the only event beginning with \e[< that's
> processed by Emacs. As soon as there's a second, completely independent
> escape also beginning with \e[< which another module would like to process,
> problems begin. Same happens with apparently many other applications.

I did mention that there's the potential for confusion already with the
X10 scheme.

> That being said, we can say that we stick to 1006, apps that are only
> interested in mouse-related \e[< codes can do the easy way of parsing, and
> apps that need to check for other \e[< codes need to do refactor more to
> implement a more correct parser.

sounds good.

--
Thomas E. Dickey <dickey@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net