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
Installing the old 0.1.0 version or the scm version on LuaRocks is severely out of date and the wiki doesn't seem to point this out. It crashes when attempting to use lspkinds.
Expected behavior
Default configs should just work. Instead you have to use rocks-git.nvim and install the main branch.
==============================================================================
care: require("care.health").check()
care.nvim ~
- Checking configuration...
- Format entry function:
- Format entry function returns correct value
- Alignments:
- All alignments are correct
- - Checking dependencies...
- Dependency 'fzy' found
Steps to reproduce
Run :Rocks install care.nvim and then use a minimal setup with require("care").setup{}.
Log
No response
Other information
No response
Minimal config
vim.env.LAZY_STDPATH=".repro"load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()
require("lazy.minit").repro({
spec= {
{
"max397574/care.nvim",
-- dependencies = {-- -- sources-- -- if you have issues with luarocks-- "romgrk/fzy-lua-native"-- },config=function()
-- keymappings, `require"care.config".setup(...)`end
},
},
-- if you have issues with luarocks-- pkg = { sources = { nil } },
})
The text was updated successfully, but these errors were encountered:
Prerequisites
Neovim Version
0.10.3
care.nvim setup
Actual behavior
Installing the old 0.1.0 version or the scm version on LuaRocks is severely out of date and the wiki doesn't seem to point this out. It crashes when attempting to use lspkinds.
Expected behavior
Default configs should just work. Instead you have to use
rocks-git.nvim
and install the main branch.Using
Healthcheck
Steps to reproduce
Run
:Rocks install care.nvim
and then use a minimal setup withrequire("care").setup{}
.Log
No response
Other information
No response
Minimal config
The text was updated successfully, but these errors were encountered: