diff options
| author | Justin M. Keyes <justinkz@gmail.com> | 2026-08-24 10:18:47 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-08-24 10:18:47 -0400 |
| commit | 8c440c469bb6f075fe26a1199ae6dcd2314394c9 (patch) | |
| tree | 88d8680226b0b1ee4e8024ffb5b750644bf3a5cb /runtime/syntax/python.vim | |
| parent | 143bbfbb1239cba40b9adc52559c358aaa69a277 (diff) | |
| download | rneovim-8c440c469bb6f075fe26a1199ae6dcd2314394c9.tar.gz rneovim-8c440c469bb6f075fe26a1199ae6dcd2314394c9.tar.bz2 rneovim-8c440c469bb6f075fe26a1199ae6dcd2314394c9.zip | |
fix(ui2): ui2 misinterprets getchar() input as pager_char (CR) #41465
Problem:
`vim.on_key()` callbacks are invoked for keys that `getchar()` consumes,
which never reach the main loop, and there is no way to tell such a key
apart. With ui2 the `on_key` handler activated after interactive
cmdline, handles it as `pager_char` (thus enters the ui2 pager).
Solution:
Skip `vim.on_key()` callbacks during `getchar()`/`getcharstr()`.
Diffstat (limited to 'runtime/syntax/python.vim')
0 files changed, 0 insertions, 0 deletions