[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates
From: |
Eli Zaretskii |
Subject: |
bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates |
Date: |
Tue, 15 Mar 2016 19:57:06 +0200 |
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Mon, 14 Mar 2016 23:03:21 +0000
> Cc: 23009@debbugs.gnu.org
>
> Added a patch. I've had to use latin-1 instead of no-conversion to prevent
> resetting the meta mode.
Not sure I understand the problem you had with no-conversion. Can you
elaborate?
> --- a/lisp/international/mule.el
> +++ b/lisp/international/mule.el
> @@ -1484,6 +1484,9 @@ set-keyboard-coding-system
> (set-keyboard-coding-system-internal coding-system terminal)
> (setq keyboard-coding-system coding-system))
>
> +(gv-define-setter keyboard-coding-system (coding-system &optional terminal)
> + `(set-keyboard-coding-system ,coding-system ,terminal))
I don't think you can do that: mule.el is preloaded, while gv.el
isn't.
It isn't a catastrophe to temporarily switch keyboard encoding "the
dull way".
> + ;; Use Latin-1 instead of no-conversion to avoid
> + ;; flicker due to `set-keyboard-coding-system' changing
> + ;; the meta mode.
Ah, so that's the problem... Did you try raw-text instead?
And anyway, doesn't latin-1 give you trouble for bytes in the 128..159
range?
Other than that, I have no comments. Let's wait for a few days to
give others time to chime in, if they want to.
Thanks.
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Philipp Stephani, 2016/03/14
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Eli Zaretskii, 2016/03/14
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Philipp Stephani, 2016/03/14
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Philipp Stephani, 2016/03/14
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates,
Eli Zaretskii <=
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Philipp Stephani, 2016/03/19
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Philipp Stephani, 2016/03/19
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Eli Zaretskii, 2016/03/25
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Philipp Stephani, 2016/03/26
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Eli Zaretskii, 2016/03/26
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Philipp Stephani, 2016/03/26
- bug#23009: 25.0.92; xterm-mouse-mode should not assume UTF-8 coordinates, Eli Zaretskii, 2016/03/27