bug#20444: paste error in emacs -nw

[Stefan Monnier]

>> What does (lookup-key input-decode-map "\e[200~") return?
> 5

Hmm... 

>> What about (lookup-key input-decode-map "\e[200")
> nil
>> and (lookup-key input-decode-map "\e[20")?
> (keymap

Hmm... even more weird.  So "\e[20" is bound to a keymap and doesn't
hide any potential "\e[200~" binding: good!

So why isn't the "\e[200~" bindings added by term/xterm.el present?

How 'bout

   (lookup-key xterm-function-map "\e[200~")
and
   (lookup-key (keymap-parent input-decode-map) "\e[200~")

And then same thing for "\e[200" and "\e[20"?

> BTW, I could reproduce similar symptoms on Debian testing with:
> emacs -Q -nw
> double-mouse-1 on "text"
> C-h k mouse-2

That's a very different issue.  In response to `mouse-2' the xterm sends
a bunch of bytes which turn into an <xterm-paste> event followed by the
pasted text (followed by the "end of paste" event).

I guess we could change the way we handle this "bracketed paste" so that
it generates a single event (an `xterm-paste') and add the text to be
pasted as "payload" directly inside the `xterm-paste' event, but it's
not a very serious issue I think.


        Stefan