-
Notifications
You must be signed in to change notification settings - Fork 37
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 wont go away (lazy.nvim luarocks) #191
Comments
Same here |
hey @kevinm6 do you know how we could avoid this? i think we don't have to force users to have a global lua 5.1 install (that fixes it) since it will be loaded by luajit anyway right? |
Pinned this and disabled rockspec until we find a workaround @abdulrahmanDev1 @kevinm6 |
Hi @3rd .. unfortunately for now it's required from Lazy the [email protected] ! rocks = {
hererocks = true
} Another pointer where it was discussed |
What I think I'm missing is why is having a specific Lua version installed externally required when the end goal is pulling luarocks that will be executed with the LuaJIT bundled by Neovim anyway - I don't think I understand how it works. Is it for a build step on some of the rocks? Or is the external Lua installation used at runtime? |
I think is due to some internals of Lazy that are really integrated with Neovim, since that's the one that needs [email protected] and the way it loads the modules at runtime. I don't think depends on something relative to LuaJIT or the rock build itself, since I'm capable of build it without Lua5.1 and in multiple ways outside NeoVim |
Hey guys @kevinm6 i'm stucked in the same point, so should i install globally lua 5.1 and also the the hererocks key on true, like this?
|
I think if you install 5.1 globally it should just work, luarocks.nvim says it needs a global LuaJIT/Lua 5.1 installation. |
Thank you @3rd |
@3rd luajit is installed with neovim when using |
Sorry, maybe I wasn't clear.. the option There are other ways you can fix it, as reported from @3rd, like just install and make lua5.1 available on $PATH or if you stick with |
Thank you guys it's fixed for me too after I added the hererocks line I tried to do it before but it didn't work out for me, |
@sebalfaro @abdulrahmanDev1 |
@kevinm6 no no, your contribution is great, so Lazy requires Lua 5.1 installed correct? |
@3rd at least in my case it wasn't necessary to install neither Lua 5.1 nor magick locally, just adding the |
Yes, Lazy requires lua5.1 for the luarocks, due to its integration.
I think should be fine if it's okay for you! |
Thanks for everyone's help in this thread. Since I didn't have any other rocks installed in my config, I found that adding the return {
{
'3rd/image.nvim',
-- Utility function to disable on Windows system
enabled = function()
if vim.fn.has 'win32' == 1 then
return false
else
return true
end
end,
dependencies = {
'leafo/magick',
},
opts = {
-- ... image.nvim config
},
},
} |
@joncrangle I think you can improve it and use Lazy return {
{
'3rd/image.nvim',
-- Disable on Windows system
cond = function()
return vim.fn.has 'win32' ~= 1
end,
dependencies = {
'leafo/magick',
},
opts = {
-- image.nvim config
}
}
} |
Any updates on this issue? |
What issue are you encountering? |
I keep getting this error whenever I open neovim although the plugin is working
The text was updated successfully, but these errors were encountered: