diff options
| author | nicm <nicm> | 2015-11-23 20:53:09 +0000 |
|---|---|---|
| committer | nicm <nicm> | 2015-11-23 20:53:09 +0000 |
| commit | 32e510bd70eedbeec8590b9bf786b11430ddaac3 (patch) | |
| tree | 9fbb34b458582bdc4e6de4d5ba3255bcec3ef238 /input-keys.c | |
| parent | 28e72ae34d43dda28ca0e6dc652eaa1179c351c7 (diff) | |
Remove support for the UTF-8 mouse extension. This was a briefly used,
poor idea that was fairly quickly replaced by SGR mouse input (which is
now widespread). It is impossible to tell the difference between UTF-8
and non-UTF-8 mouse input; since the mouse-utf8 option was removed tmux
has not handled it correctly in any case; and it is ridiculous to have
three different forms of mouse input.
Diffstat (limited to 'input-keys.c')
| -rw-r--r-- | input-keys.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/input-keys.c b/input-keys.c index 2915cb45..4fee2f58 100644 --- a/input-keys.c +++ b/input-keys.c @@ -243,17 +243,11 @@ input_key_mouse(struct window_pane *wp, struct mouse_event *m) * is because an old style mouse release event cannot be converted into * the new SGR format, since the released button is unknown). Otherwise * pretend that tmux doesn't speak this extension, and fall back to the - * UTF-8 (1005) extension if the application requested, or to the * legacy format. */ if (m->sgr_type != ' ' && (wp->screen->mode & MODE_MOUSE_SGR)) { len = xsnprintf(buf, sizeof buf, "\033[<%u;%u;%u%c", m->sgr_b, x + 1, y + 1, m->sgr_type); - } else if (wp->screen->mode & MODE_MOUSE_UTF8) { - len = xsnprintf(buf, sizeof buf, "\033[M"); - len += utf8_split2(m->b + 32, &buf[len]); - len += utf8_split2(x + 33, &buf[len]); - len += utf8_split2(y + 33, &buf[len]); } else { if (m->b > 223) return; |