Back to articles
Migrating To Neovim v0.12.0 Challenge Faced And Solution Found
How-ToTools

Migrating To Neovim v0.12.0 Challenge Faced And Solution Found

via Dev.toKevin Asaria

A week ago I saw that there was a new version of Neovim(v0.12.0) out and I decide to upgrade to it. These are the challenges that I faced and how I solved it. Context, as is required nowadays. I use LazyVim to transform the basic neovim to be a capable IDE. And indeed I do not do much configuration cause I have not learnt to and the out of the box experience has served me well. I just install LSPs through mason and so far I have not faced any issue. I thought that switching to neovim v0.12 would be as easy as downloading the binary , deleting the current one and replacing it with the new one. Easy peasy lemon squeezy. However, I came across a problem whereby the UI broke and I kept getting this error E5108: Lua: vim/_core/editor.lua:0: nvim_exec2()[1]..BufReadPost Autocommands for "*": Vim(append):Lua callback: /usr/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:208: /usr/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:391: attempt to call method 'set_timeout' (a nil val

Continue reading on Dev.to

Opens in a new tab

Read Full Article
2 views

Related Articles