4 ms·
just use lazyvim[1] and be done with it! some people takes care of the compatibility and they are probably more competent than you (i mean a newcomer who starts
by ossusermivami 2y ago
just use lazyvim[1] and be done with it! some people takes care of the compatibility and they are probably more competent than you (i mean a newcomer who starts writing their nvim config)
[1] https://www.lazyvim.org/ https://www.lazyvim.org/
- satvikpendem 2y agoClearly you didn't read any of the threads as it is sometimes even lazyvim that causes these incompatibilities: https://old.reddit.com/r/neovim/comments/1dgtyzw/lazynvim_doesnt_like_lualinenvim/ https://old.reddit.com/r/neovim/comments/1dgtyzw/lazynvim_do... https://old.reddit.com/r/neovim/comments/1dp47gi/lazyvim_ownership_issue/ https://old.reddit.com/r/neovim/comments/1dp47gi/lazyvim_own...
- SpaceNugget 2y agoOne of those threads is about lazy.nvim, not lazyvim. The other is a question about what to do after accidentally installing lazyvim with the wrong shell on windows, not about plugin updates breaking things.
- satvikpendem 2y agoLazyvim is powered by lazy.nvim, at some point it'll break. These are example posts, you can feel free to go through reddit for more examples but yes Neovim does routinely break more for me than VSCode ever does, which is basically never.
- ossusermivami 2y agoit never has been my experience! i have used lazyvim distro for the last year or so and run some :Lazy update for time to time and usually i just need to close neovim and restart and it will all be working well.. I think i had an issue when they moved to conform.nvim from the deprecated language server based method but that's maybe about it (I deleted the nvim cache and it was all good after)