-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when starting Neovim. Suggestions and add-ons do not work. #669
Comments
Try installing |
I Have |
I also have curl installed, but I specifically changed the permissions on it because my organization prohibits the use of outside downloads. What is being downloaded through curl? Is there any way to configure a proxy? |
The prebuilt binary for the fuzzy matching. You could:
|
@HertelP You seem to be having a different issue, are you on neovim 0.10+? |
@Saghen the error is there because gsub also adds the number of replacements to the result. blink.cmp/lua/blink/cmp/health.lua Line 28 in bff6c0f
and it is due to the above line. It can be fixed with replacing this line with: or vim.uv.fs_stat(string.gsub(download.lib_path, 'libblink_cmp_fuzzy', 'blink_cmp_fuzzy'):match('(.+)%s*%d*$')) |
Ahh thanks! Fixed that on main |
I had the same error with 0.7.6, which got resolved by building the fuzzy lib manually. However I just upgraded to 0,8.0 and now it fails in the same place.. this time because download.lib_path is null:
|
Root issue was solved by manually installing or building since the OP couldn't use curl. The issues around health check were solved on main |
@Saghen |
Make sure you have done the following
blink.cmp
Bug Description
After running neovim (I use lazyvim), I get an error in python, javascript, etc files.
Startup error Python file
Startup error JS file
checkhealth
After skipping it, the suggestions do not work. Default blink configuration from lazyvim
Relevant configuration
No response
neovim version
NVIM v0.10.2 Build type: Release LuaJIT 2.1.1713484068 Run "nvim -V1 -v" for more info
blink.cmp
version: branch, tag, or commitbranch main
tag v0.7.6
commit ae5a4ce
The text was updated successfully, but these errors were encountered: