Replies: 2 comments
-
|
Yep, seem to have a similar issue with Neorg. I can't setup with config errors. Environment:
Error: Versions Tried:
Attempted Fixes:
|
Beta Was this translation helpful? Give feedback.
-
|
Yep, seem to have a similar issue with Neorg. I can't setup with config errors. Environment:
Error: Versions Tried:
Attempted Fixes:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So, I have neovim 0.11.4, rocks.nvim as plugin manager with neorg 9.3.0 installed. I also have nvim-treesitter-legacy-api 0.9.2 since neorg requires it (but doesn't have it as dependency for some reason, wasn't it the whole point of rocks.nvim?) and will barf at startup without it installed. I also have rocks-treesitter.nvim and a bunch of tree-sitter-* plugins for every language I use, including neorg.
The problem is that nvim-treesitter-legacy-api seems to be broken. Or maybe neorg tree-sitter related code is broken. Or it conflicts with rocks-treesitter. Or I don't know.
The symptoms so far is that opening any .c files produces endless stream of errors like
Which appear for basically every keystroke and essentially lock up neovim.
According to google that was a bug years ago and every issue that mentions this error message is closed as resolved.
Another symptom is
:checkhealth nvim-treesittersayserrors found in the query, try to run :TSUpdate {lang} ~yet:TSUpdatecommand is unavailable.I kinda blame neorg here since it looks like the error is coming from this legacy-api plugin and it is a crutch for neorg but maybe my blame is misplaced.
So, what is the proper way to have neorg without breaking tree-sitter for other languages?
Beta Was this translation helpful? Give feedback.
All reactions