1gg hangs neovim

[xzfc]

More generally, it seems that two-letter commands starting with 1 hang neovim (e.g., 1gg, 10dd). But, e.g., 9dd and 10} work fine.

Probably related to #17.

$ nvim --version | head -3
NVIM v0.5.0
Build type: Release
LuaJIT 2.1.0-beta3

[folke]

I'm not able to reproduce this. Can you make a minimal config to trigger this?

[xzfc]

Found the offending keybinding: 1gD. Minimal config based on #117:

if !filereadable('/tmp/plug.vim')
  silent !curl --insecure -fLo /tmp/plug.vim
    \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
endif

source /tmp/plug.vim
call plug#begin('/tmp/plugged')
Plug 'folke/which-key.nvim'
call plug#end()

autocmd VimEnter * PlugClean! | PlugUpdate --sync | close

lua << EOF
require("which-key").setup{}
EOF

" https://github.com/neovim/neovim/blob/5d6ecfa3c7447009da75842c611ea1b9f1db83e7/runtime/doc/lsp.txt#L50
nnoremap <silent> 1gD   <cmd>lua vim.lsp.buf.type_definition()<CR>

nvim --noplugin -u basic.vim basic.vim

[folke]

That's a really odd key binding. Not sure what that one was chosen to be put in the docs. Either way, I'll see if I can fix this properly.

[folke]

I think that's actually a typo in the LSP docs 😅

A better set of default bindings can be found on the lspconfig readme

[folke]

Can you check wether it even works with that binding without WhichKey?

[xzfc]

I think it's mimicking a built-in vim mapping 1gD. And this binding example is already removed from the latest neovim docs. It works tho.

I can solve it for me by removing it from my config (since I'm not using this particular mapping anyway), but IMO which-key shouldn't hang if a weird but valid mapping is present.

[folke]

I just pushed a fix for this. Thank you for reporting!

[xzfc]

Thanks!