-
-
Notifications
You must be signed in to change notification settings - Fork 202
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
Failed to load parser for norg #1473
Comments
For me installing the parser fails with
|
Do you have luarocks installed? |
Yes, I do, I also checked and it's on the PATH and I can run it from there and the Lazy.nvim health check also can find it. |
Hmm I wonder why it's telling you to downgrade your lua version 🤔 |
Do you have the |
@jan-xyz - I had a similar issue when trying to install |
oh sorry, then please disregard my case. I will split it out if I cannot figure it out. I have luajit install and it is still broken :(
I am using the latest lazy.nvim version and according to the announcement by folke on Reddit, it's not needed anymore? I will dig a bit and see if there is something wrong and then open a separate issue since this seems to be about some other error. https://www.reddit.com/r/neovim/comments/1dng1d6/lazynvim_110_is_released_packages_luarocks_and/ EDIT: just found this GitHub issue and it is a problem on lazy.nvim side. |
because they need to "downgrade their lua version"... Just install lua5.1 and it'll work. Reason being that lua5.1 is the version that's compatible with neovim, so that's what lazy checks for. It's possible for lazy to update and require lua5.1 or luajit, but that's not the case last I checked (like 2 days ago). |
But Lua v5.3.6 works for me |
well then that's nice for you |
Prerequisites
Neovim Version
NVIM v0.10.0 Build type: Release LuaJIT 2.1.1713484068 Run "nvim -V1 -v" for more info
Neorg setup
Actual behavior
Running
:Neorg sync-parsers
results in errors when I run:checkhealth nvim-treesitter
like the following:Expected behavior
No errors when compiling/installing parsers.
Steps to reproduce
Running on an M3 mac:
Potentially conflicting plugins
No response
Other information
No response
Help
None
Implementation help
No response
The text was updated successfully, but these errors were encountered: