aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/viml/parser/expressions.c
diff options
context:
space:
mode:
authorsymphorien <symphorien@users.noreply.github.com>2018-04-22 17:26:04 +0000
committerJustin M. Keyes <justinkz@gmail.com>2018-04-22 19:26:04 +0200
commitffb89049131a1e381c7d2b313acb953009bae067 (patch)
tree7daa74157100c3d7036818fed90ec8adbcf4bf0e /src/nvim/viml/parser/expressions.c
parentd05712fbe7b56789b6fc5c205ef7b928cd3fb722 (diff)
downloadrneovim-ffb89049131a1e381c7d2b313acb953009bae067.tar.gz
rneovim-ffb89049131a1e381c7d2b313acb953009bae067.tar.bz2
rneovim-ffb89049131a1e381c7d2b313acb953009bae067.zip
tui/input.c: add support for mouse release events in urxvt (#8309)
Some terminals don't report which buttons are involved in some mouse events. For example, the urxvt protocol (http://www.huge-man-linux.net/man7/urxvt.html section "Mouse reporting") does not report which button has been released. In this case libtermkey reports button 0 (http://www.leonerd.org.uk/code/libtermkey/doc/termkey_interpret_mouse.3.html) Up to now, forward_mouse_event did not handle button==0. On press events there is not much we can do, and we keep the current behavior which is dropping the event. But on drag-and-release events we can compensate by remembering the last button pressed. fixes #3182 for urxvt fixes #5400
Diffstat (limited to 'src/nvim/viml/parser/expressions.c')
0 files changed, 0 insertions, 0 deletions