Neovim-from-scratch icon indicating copy to clipboard operation
Neovim-from-scratch copied to clipboard

error while calling lua chunk (nvim tree-sitter part)

Open Nikhil-John opened this issue 2 years ago • 6 comments

Hi, So this is my 3rd time trying this config (3 separate installs). Used to be working fine last 2 times but this time it shows this error: nvim

Also would be helpful if I could get help on how to fix the error given by nvim-cmp too.

Thanks in advance

Nikhil-John avatar May 23 '22 17:05 Nikhil-John

Go to treesitter config file and change ensure_installed = "maintained" to ensure_installed ={maintained} and then run PackerSync

miastorga avatar May 28 '22 16:05 miastorga

Go to treesitter config file and change ensure_installed = "maintained" to ensure_installed ={maintained} and then run PackerSync

thanks for the answer :handshake: You can find it in the folder ~/.config/nvim/lua/user/treesitter.lua

Mr-JZ avatar May 28 '22 20:05 Mr-JZ

this will be fixed when #131 is merged. Nvim-cmp error is fixed on master branch

gnmearacaun avatar May 31 '22 20:05 gnmearacaun

Go to treesitter config file and change ensure_installed = "maintained" to ensure_installed ={maintained} and then run PackerSync

Thanks that worked great. Now when I open nvim I see a text with a link which leads to a migration guide. May I know if I should be bothered about this?

Thanks :3 image image

Nikhil-John avatar Jun 18 '22 17:06 Nikhil-John

Thanks that worked great. Now when I open nvim I see a text with a link which leads to a migration guide. May I know if I should be bothered about this?

I read through the migration guide, and from what I gathered, the error is referring to any occurrences of "g:"-style settings in the configuration. I couldn't find any such settings in the LunarVim repo, but I'm guessing they could still be lingering somewhere in one or more of the dependencies.

That could potentially be a huge task if my hypothesis is correct. Perhaps someone who has given it more thought or investigation could disprove it.

As far as I can see though, the message is more likely to be an annoyance rather than broken core functionality of the configuration.

brianrobt avatar Jun 22 '22 21:06 brianrobt

Referencing #124.

brianrobt avatar Jun 22 '22 21:06 brianrobt