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
First, thanks for the huge effort on this amazing plugin. Has been a great companion for me.
For some reason after the 0.6.0 and 0.6.1 update I am getting this error:
Error 19:58:20 msg_show.lua_error Error executing vim.schedule lua callback: ...l/share/nvim/lazy/blink.cmp/lua/blink/cmp/fuzzy/init.lua:24: attempt to call field 'fuzzy_matched_indices' (a nil value)
stack traceback:
...l/share/nvim/lazy/blink.cmp/lua/blink/cmp/fuzzy/init.lua:24: in function 'fuzzy_matched_indices'
.../lazy/blink.cmp/lua/blink/cmp/windows/render/context.lua:21: in function 'get_from_items'
...vim/lazy/blink.cmp/lua/blink/cmp/windows/render/init.lua:54: in function 'draw'
...im/lazy/blink.cmp/lua/blink/cmp/windows/autocomplete.lua:111: in function 'open_with_items'
.../.local/share/nvim/lazy/blink.cmp/lua/blink/cmp/init.lua:57: in function <.../.local/share/nvim/lazy/blink.cmp/lua/blink/cmp/init.lua:51>
Version 0.5.1 is working fine. I using it for now, but I can help to test this issue.
Hey there, it seems likely the downloader failed to get the new prebuilt binary, something I've been tracking in #68 but have had trouble reproducing... Does reinstalling the plugin solve the issue for you?
@Saghen I will try. But I have confirmed that the download is failing. It's getting another binary than x86_64-apple-darwin.dylib. Doing manual download and rename works fine.
Make sure you have done the following
blink.cmp
Bug Description
First, thanks for the huge effort on this amazing plugin. Has been a great companion for me.
For some reason after the 0.6.0 and 0.6.1 update I am getting this error:
Version 0.5.1 is working fine. I using it for now, but I can help to test this issue.
I am using on OSX 10.15.7.
Relevant configuration
neovim version
NVIM v0.11.0-dev-1220+gd9b08c58c3
blink.cmp
version: branch, tag, or commitv0.6.1
The text was updated successfully, but these errors were encountered: