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
After I press enter without selecting an item, I get this:
In order to make it work properly, now I just remove the buffer map <cr> when loading autopairs, and use a global mapping to map <cr> with auto indent functionality:
This is weird, this situation only happend on <cr>, auto-pairs also bind <space> with some other functionality, and I bind <space> to accept the first one in keymap of blink, and it works well.
Seems same issue as #441 .
Current blink.cmp would identify keymap by desc , so after jiangmiao/auto-pairs reset keymap would cause problem in blink side. Should be fix after #487 merged.
Update keymap logic in jiangmiao/auto-pairs should also works, but seems the repo has been unmaintained.
Seems same issue as #441 . Current blink.cmp would identify keymap by desc , so after jiangmiao/auto-pairs reset keymap would cause problem in blink side. Should be fix after #487 merged.
Saghen
changed the title
Keymap with buffer type map not work expectedly when binding them with keymap in blink
Keymap fallback doesn't handle script mappings
Jan 3, 2025
Make sure you have done the following
blink.cmp
Bug Description
I use
jiangmiao/auto-pairs
for auto close the braces and auto delete the close brace when deleting the open one, and auto indent after typing<cr>
.I use the below configuration for this plugin with
lazy
:This plugin will add some buffer type keybindings, for example the
<cr>
will be binded like this:Then I use
keymap
in blink to bind<cr>
:After I press enter without selecting an item, I get this:
In order to make it work properly, now I just remove the buffer map
<cr>
when loadingautopairs
, and use a global mapping to map<cr>
with auto indent functionality:Relevant configuration
No response
neovim version
NVIM v0.10.1
blink.cmp
version: branch, tag, or commitv0.8.1
The text was updated successfully, but these errors were encountered: