Play nicely with keybind combinations that assume timeoutlen > 0 about vim-which-key HOT 4 CLOSED

vim-leader-guide has no issue with the gcc case in that it uses input() to interact with users. The weakness of input() is that it can't respond quickly when you trigger an invalid item IMO. vim-which-key uses getchar() to get input from users and is able to give an instant response when your input is invalid. I don't know there is a way to achieve an additional whichkey specific timeout. For now, the workaround is to remap gcc to avoid this case. Anyway, I will see if there are something I can do.

from vim-which-key.

i have tried g:which_key_timeout config, but there is not any effects. everything is same as before.
without timeoutlen, WhichKey menu takes 1s to show up.

from vim-which-key.

@yaahallo Hello, can you try this branch which I add a specific timeout for vim-which-key. Now it should be able to distinguish groups like gc and gcc. By default the timeout introduced is same with the option timeoutlen.

" By defualt it's same with `timeoutlen`
let g:which_key_timeout = 300

from vim-which-key.

3f54404 should resolve #4 as well, please give it a test.

from vim-which-key.