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
I'm trying out this plugin with LazyVim and noticed that the <C-k> keybinding is instead being bound for LSP signature help by LazyVim.
After adding vim.notify statements to the functions that add keybindings for both blink.cmp and LazyVim's LSP, I found that LazyVim's bindings are being set after blink.cmp, overwriting the mapping.
Interesting to note is that this works in nvim-cmp because they set key bindings on the first InsertEnter.
The text was updated successfully, but these errors were encountered:
stefanboca
changed the title
<C-K> keymap overwritten by LazyVim LSP keymap
<C-k> keymap overwritten by LazyVim LSP keymap
Oct 8, 2024
I just pulled the latest changes and this issue still persists. It looks like 506ea74 fixes the case where blink overrides pre-existing buffer mappings. However, my issue is that blink is binding <C-k>, which is then overwritten by LazyVim.
I believe the reason I didn't previously have this issue with nvim-cmp is because nvim-cmp sets keymaps on the InsertEnter event, rather than on BufEnter (which occurs after LazyVim sets the <C-k> keybind, overriding blink).
I'm trying out this plugin with LazyVim and noticed that the
<C-k>
keybinding is instead being bound for LSP signature help by LazyVim.After adding
vim.notify
statements to the functions that add keybindings for both blink.cmp and LazyVim's LSP, I found that LazyVim's bindings are being set after blink.cmp, overwriting the mapping.Interesting to note is that this works in
nvim-cmp
because they set key bindings on the firstInsertEnter
.The text was updated successfully, but these errors were encountered: