LunarVim VS LazyVim

LunarVim

I would suggest to start getting into vim by first trying out popular vim keybinding plugins available on your favorite code editor and get used to those first. Then, if you want to dive deeper into the power of Neovim, try out popular configs like LazyVim, LunarVim, NvChad... Taking Neovim from a mere text editor to a full-featured IDE with features like intellisense, debugging, testing, etc... on your own takes quite a lot of work and configuration.

I used Helix for a while due to its support for LSP out-of-the-box, which my Vim config at the time couldn't live up to. I switched back to NeoVim after finding LunarVim[1] which had everything I was trying to get setup in my own config.

[1] https://www.lunarvim.org/

I'll admit I didn't look into it, but Helix sounds like something like LunarVim (https://www.lunarvim.org/)

Personally I much prefer that the editor NOT ship with something like that by default, especially when it's so easy to set up. I have several different vim config I use, including a pretty bare-bones one for headless systems, and I much prefer the ability to customize something very specifically.

Build tools that can compose together, rather than a single do-it-all tool. That is the power of the low level editors vs IDE's.

I can't comment on any implementation details, but at least with LunarVim (which I use for daily coding), a slowdown when interacting with LSP is very noticeable. Some others have attested to this on a GitHub issue.

I'm not doubting your experiences with the lack of a slowdown, but there is truth that others do experience it. That might be more of a problem with LunarVim itself rather than Vim, but how likely am I (as someone who would like to avoid what he calls "config hell") or other newcomers to avoid whatever pitfalls there are, if a distribution designed for ease of use by people who know better fall into them?

https://github.com/LunarVim/LunarVim/discussions/3359

Anyways, although i have not used them, LazyVim and LunarVim comes highly recommended. You can try these and see what suits you .

Please take a look at this issue. The culprit is the path source of nvim-cmp.

I’m having trouble understanding the preffered file structure when using lazy. I have a setup that works currently and I used this guide but I believe that this configuration defeats the purpose of lazy-loading. I also tried moving all of the plugin configs to the /nvim/plugins folder but that didn’t work, I think because when using lazy you want lazy to handle the loading not RTP. I’ve taken a look at the lazyvim github but I’m a little bit overwhelmed. I don’t understand how their nvim/init.lua doesn’t point to anything with require. Here is my config. So I think that the mistake I’m making is loading all my plugins in a table that gets passed to lazyvim but then requiring configs from my init.lua, when all of that info should get passed directly to lazy vim via multiple lua tables?

Has presets for each default plugin module in LazyVim.

I have been looking at LazyNvim and LazyVim and I would like to do something similar to in particular LazyNvim's startup text. How do configurations like this create this startup text?

See this Lazyvim issue.

You can try to mimic how LazyVim loads alpha here https://github.com/LazyVim/LazyVim/blob/main/lua/lazyvim/plugins/ui.lua

As usual, I referred to how folke does stuff for inspiration, and I want to better understand what exactly is going with the Treesitter configuration in LazyVim.

LazyVim (This is a distro in the form of a plugin, imo beats astronvimm nvchad, lunarvim for that reason alone. Check out the plugins/extras/lang directory in there. Has setup for a few languages. You can see the list here. Just raise a request for JAVA and someone will have your back))

Anyways, although i have not used them, LazyVim and LunarVim comes highly recommended. You can try these and see what suits you .

Am I reading this correctly, in the LazyVim starter, this line reads as it's importing all the plugins from the remote GitHub project, is that correct?