[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xte
From: |
Alex |
Subject: |
bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode) |
Date: |
Wed, 08 Nov 2017 14:57:45 -0600 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux) |
Olaf Rogalsky <olaf.rogalsky@t-online.de> writes:
> Hi,
Hi,
Thanks for looking into this. It looks like the only issue remaining is
#2 (M-mouse-1).
> PSS: I don't think, that #29143 is related. Both, `Evil-mode' *and*
> `xterm-mouse-mode' fool around with the ?\e prefix in the
> `input-decode-map', but they obviously do it in an incompatible
> way.
It's not that. I checked out evil-mode's code and found out that it uses
a modified ~6 year old version of `mouse-drag-track', which evidently
doesn't play too well with recent Emacs versions.
For example, try using the definitions of `mouse-drag-region' and
`mouse-drag-track' of Emacs 24 in Emacs 25/26. Then in
`xterm-mouse-mode', releasing `mouse-1' inserts the control sequence
into the current buffer (which is what Bug#29143 is, except in
evil-mode, the characters in the sequence are not all bound to
`self-insert-command').
This old code uses `read-event', which, as you mentioned in your other
reply, doesn't use `input-decode-map'. Replacing it with:
(aref (read-key-sequence-vector nil) 0)
fixes Bug#29143.
Eli, Stefan, does it make sense that `read-event' doesn't take into
account `input-decode-map'? If so, then is there a better alternative to
the above workaround? Perhaps there could be a new optional argument to
`read-event'?
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), (continued)
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Olaf Rogalsky, 2017/11/06
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Eli Zaretskii, 2017/11/11
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Alex, 2017/11/12
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Eli Zaretskii, 2017/11/12
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Alex, 2017/11/12
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Eli Zaretskii, 2017/11/13
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Olaf Rogalsky, 2017/11/13
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Eli Zaretskii, 2017/11/13
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Olaf Rogalsky, 2017/11/13
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Stefan Monnier, 2017/11/12
bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode),
Alex <=
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Alex, 2017/11/08
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Stefan Monnier, 2017/11/08
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Alex, 2017/11/09
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Stefan Monnier, 2017/11/09
- bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode), Eli Zaretskii, 2017/11/09