diff options
| author | fredizzimo <fsundvik@gmail.com> | 2025-09-14 00:57:04 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-13 14:57:04 -0700 |
| commit | 8ae9a44d3841e3ae39f3976a711b29bb50b8f515 (patch) | |
| tree | a720c0230e215387531162c1d861a3addc1ca0a1 /runtime/lua/vim/shared.lua | |
| parent | c1648cf820ed379f6abb7cb802680a02a1def755 (diff) | |
| download | rneovim-8ae9a44d3841e3ae39f3976a711b29bb50b8f515.tar.gz rneovim-8ae9a44d3841e3ae39f3976a711b29bb50b8f515.tar.bz2 rneovim-8ae9a44d3841e3ae39f3976a711b29bb50b8f515.zip | |
feat(ui): support grid=0 in nvim_input_mouse #32535
Problem:
Multigrid UIs have to find out which window to send the input by using
the Nvim focus rules, which are not fully documented.
Furthermore,`getmousepos()` has several problems when multigrid is
enabled, with the main one being that screenrow and screencol are window
relative instead of screen relative, due to the fact that the UI don't
send any absolute coordinates.
Solution:
Allow passing 0 as grid to `nvim_input_mouse`, with absolute
coordinates, which lets nvim determine the actual window to send the
mouse input to. This works as long as nvim is in charge of the window
positioning. If the UI repositions or resizes the windows, it can still
pass the grid it determines like before.
Diffstat (limited to 'runtime/lua/vim/shared.lua')
0 files changed, 0 insertions, 0 deletions