Problem when running on command line vim on Windows about vim-which-key HOT 4 CLOSED

Hello @liuchengxu after some research I found out that the problem is in file which_key/window.vim in the following lines (57):

  augroup which_key_cursor
    autocmd!
    execute 'autocmd BufLeave <buffer> set t_ve=' . &t_ve
    execute 'autocmd VimLeave <buffer> set t_ve=' . &t_ve
  augroup END

The error is because in windows cmd the t_ve has a value of ^[|V which needs to be escaped. So if you change the execute lines like this it won't throw the error anymore:

    execute 'autocmd BufLeave <buffer> set t_ve=' . escape(&t_ve, '|')
    execute 'autocmd VimLeave <buffer> set t_ve=' . escape(&t_ve, '|')

If you can confirm that this actually resolves the error I'd be happy to provide a PR!

from vim-which-key.

I can reproduce in cmd vim and powershell, but after the error message has been echoed, vim-which-key still works and the message never appears again. Git Bash doesn't have this issue. Will look into this later.

from vim-which-key.

Hello @liuchengxu in my case it is not working properly after the error has been echoed. What happens after that error is that whenever I press a key I see a non printable character in insert mode and that printable character and the character in command mode. This is really strange to explain so I'll provide a screenshot:

This is how my vim looks like after I've triggered the error and tried writing "Hello" to both the main buffer and the command prompt! The non printable character has the value of ESC ("1b" in ASCII)

from vim-which-key.

Good, I also just found the root cause! I can confirm your solution works, please open up a PR.

from vim-which-key.