You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use vim-plug, try to update the vim-which-key plugin with :PlugUpdate. I also had issues with the <cr> key, but liuchengxu added support for that key. ;-)
I don't know the state of things when lifeBalance had things working.
Reproduced OP's report with:
let mapleader = "\<CR>"
let g:map = {}
let g:map.l = {'name':'+holiday', '1': ['echom ''merry xmas''', 'say greeting']}
call which_key#register('<CR>', 'g:map')
nnoremap <leader> :WhichKey '<CR>'<CR>
:WhichKey '<CR>' works as reported in command mode, but in normal mode doesn't.
I suppose this may have to do with the use of <args> in which_key#start(). Replacing that with <q-args> might help with this specific case, it might do some escape and un-escape magic.
Suggested workaround:
let F=function({->execute(':WhichKey "<CR>"','')})
nnoremap <leader> :call F()<CR>
Could probably make that a one-liner if you wanted.
Environment (please complete the following information):
Describe the bug
:WhichKey "<CR>"
works when typing it by hand, but mapping it to a key produces message:To Reproduce
Steps to reproduce the behavior:
:nnoremap :WhichKey "<CR>"<CR>
Expected behavior
Whichkey should function as it normally does in command mode
The text was updated successfully, but these errors were encountered: