Closed atweiden closed 1 year ago
You haven't said which terminal (and version) you are using, which operating system, or which Vim version, so I can make only general comments and I can't test whether it works for me in that configuration.
You can check if Fixkey_setup()
is being called via :echo g:Fixkey_termType
.
Maybe your terminal isn't providing a response to Vim's terminal setup such that the TermResponse
event isn't being sent. You can put an echoerr 'got TermResponse'
in the Fixkey_termReponse()
function to test this.
You can adjust the time delay in your ~/.vimrc
via let g:Fixkey_setupDelay = 10
(or other values). The default is now 400
.
Thanks for the help. It seems to be a tmux issue. The same regression occurs with tmux on both macOS (Terminal.app and iTerm2, macvim-9.0.1276) and Linux (foot, vim-9.0.1321)
You can check if Fixkey_setup() is being called via
:echo g:Fixkey_termType
.
g:Fixkey_termType
is undefined in tmux, defined otherwise.
You can adjust the time delay in your
~/.vimrc
vialet g:Fixkey_setupDelay = 10
(or other values). The default is now 400.
Setting g:Fixkey_setupDelay = 10
doesn’t affect the outcome.
Thanks for the additional details. It turns out that the TermResponse
autocmd is not sent for all terminals (notably not for tmux, PuTTY, and Linux console). I've released version 0.3.15 which uses the VimEnter
autocmd as a fallback to ensure that Fixkey setup runs in all cases.
Tyvm.
Reverting 454c19d1274679a8b34b7fe9bda18cae90852431 fixes keybindings for me. I haven’t investigated why.