Closed Martin1887 closed 1 year ago
It may not be a problem with which-key since I have the same error and dont use it.
Neovim version :
NVIM v0.10.0-dev-1304+gdadc06ced-dirty
Build type: RelWithDebInfo
LuaJIT 2.1.1696795921
Error :
Failed to run `config` for legendary.nvim
...e/nvim/lazy/legendary.nvim/lua/legendary/data/keymap.lua:40: 1: expected string, got nil
# stacktrace:
- vim/shared.lua:0 _in_ **validate**
- /legendary.nvim/lua/legendary/data/keymap.lua:40 _in_ **parse**
- /legendary.nvim/lua/legendary/init.lua:49
- vim/shared.lua:0 _in_ **tbl_map**
- /legendary.nvim/lua/legendary/init.lua:45 _in_ **keymaps**
- /legendary.nvim/lua/legendary/init.lua:138 _in_ **keymap**
- /legendary.nvim/lua/legendary/init.lua:89 _in_ **setup**
- ~/.config/nvim/lua/ls-devs/plugins/legendary.lua:5 _in_ **config**
It's a problem with the lazy.nvim integration. Looks like the API changed to return the left-hand-side of the keymap as keymap.lhs
where it used to be keymap[1]
.
Pushing up a PR to fix right now...
Fixed in version 2.12.2 which I just tagged.
Similar Issues
Neovim Version
0.9.2
Steps to Reproduce
Expected Behavior
No errors
Actual Behavior
Minimal Configuration to Reproduce
Output from :LegendaryLog
``` [lun 09 oct 2023 09:14:39][legendary.nvim] Took 1.00482 ms to filter items in context. [lun 09 oct 2023 09:14:39][legendary.nvim] Launching select UI ```:LegendaryLog
output (click to expand)Additional Details and/or Screenshots
It may be a problem with which-key because items from which-key seem to not be registered.