-
Has anyone run into this runtime error? Error executing vim.schedule lua callback: vim/keymap.lua:0: Invalid (empty) LHS
stack traceback:
[C]: in function 'nvim_set_keymap'
vim/keymap.lua: in function 'set'
...ges/start/vimplugin-which-key/lua/which-key/mappings.lua:302: in function 'create'
...ges/start/vimplugin-which-key/lua/which-key/mappings.lua:314: in function 'parse'
...kages/start/vimplugin-which-key/lua/which-key/config.lua:327: in function 'add'
...kages/start/vimplugin-which-key/lua/which-key/config.lua:285: in function ''
vim/_editor.lua: in function <vim/_editor.lua:0> It only happens after I upgrade some mappings to the new suggested syntax, e.g. Checking for issues with your mappings ~
- WARNING You're using an old version of the which-key spec.
Your mappings will work, but it's recommended to update them to the new version.
Please check the docs and suggested spec below for more info.
Mappings: >
{
["<leader>n"] = {
d = { "<cmd> NoiceDismiss <CR>", "Dismiss notifications" },
name = "Noice"
}
}
-- Suggested Spec:
{
{ "<leader>n", group = "Noice" },
{ "<leader>nd", "<cmd> NoiceDismiss <CR>", desc = "Dismiss notifications" },
} Using the latest master and Neovim v0.10.3. |
Beta Was this translation helpful? Give feedback.
Answered by
gvolpe
Jan 6, 2025
Replies: 1 comment
-
Sorry, I confused the |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
gvolpe
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry, I confused the
folke
repo, this is now reported in thewhich-key
repo.