nvim-lazyman VS LazyVim

I made Github Pages from some of my repositories. It's a nice feature, thanks!

$NVIM_APPNAME might help if the distro's file structure doesn't work with your git model (like, AstroNvim wants you to use a sub-theme-thing for your personal config customizations, and this might not be graceful to implement as just a separate git branch). https://gist.github.com/elijahmanor/b279553c0132bfad7eae23e34ceb593b has some shell functions using nvim_appname for easily switching between different config repos and even https://github.com/doctorfree/nvim-lazyman for trying out different distros.

I haven't posted much about lazyman because I'm busy working on it and it is changing rapidly. Also, as you can see, a lot of my time is spent dreaming up Neovim configuration management fantasies.

There are many excellent distributions, personal configurations, and custom configurations to study. I wrote a Neovim configuration manager to make it easy for me to install, initialize, and explore multiple Neovim configurations. Most of the popular Neovim distributions and configurations are supported in this tool.

I'm also a fan of these preconfigured Neovim configurations. I've learned a lot by exploring many of them. To help me install and initialize multiple Neovim configurations I wrote Lazyman, a Neovim configuration manager. Currently Lazyman supports over 40 Neovim configurations.

This one has a good collection of configs, from simple to complicated: doctorfree/nvim-lazyman

See https://github.com/doctorfree/nvim-lazyman for info on Lazyman.

Currently lazyman supports Neovim configurations using the Lazy, Packer, and vim-plug plugin managers. Not all Neovim configurations install and initialize cleanly. Some have hard-coded paths assuming ~/.config/nvim as the configuration location. Others do not initialize cleanly from the command line (nvim --headless ...). However, many configurations not supported out-of-the-box by lazyman can be installed and initialized. If you find an interesting configuration that works well with Lazyman or if your favorite config does not initialize cleanly with Lazyman then open an issue at https://github.com/doctorfree/nvim-lazyman/issues

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?