nvchad_config VS dotfiles

I have been versioning my .dotfiles and nvchad setup for a while now. Lately I realized that not everyone was taking as much care/versioning it at all so I wanted to make a poll and get some actual opinions on it! Feel free to post links to your setups too.

A personal favorite is how much you can personalize vim. Everything is customizable, from your background color to very specific keybindings. One example of that would be my own .vimrc. As someone who gets irritated as soon as something tiny is wrong with their code editor, the ability to customize everything was a very big bonus. Currently I am using nvchad with my own nvchad config, which makes for a beautiful code editor:

i find event = { 'BufReadPre', 'BufNewFile' } is enough

i use a bare git repo that manages files in my $HOME, (two actually, one for both windows and Linux and one just for windows). within my dotfiles i have a script (for only windows right now) that installs everything and sets up ssh for a new machine.

i version both in the same repo. here: https://github.com/pynappo/dotfiles/tree/main/.config/nvim

you can see a more explicit setup in my config without the opts stuff and my server configs here

here was an old version of my dotfiles that did that with lazy

your original code has the correct idea if you wanted to load a script with require() (and it's what i did back when i used packer.nvim), but you're misunderstanding what require("lazy").setup("plugins") does. check the readme again.

you're supposed to have a /lua/plugins/ folder with lua files with your lua specs. like I have my lazy.nvim get it's plugin specs from the /lua/pynappo/plugins folder

anyways my config isn't great but I do use it on windows

basically I have a file that stores all my keymaps grouped into different tables, and I have a tiny helper function that can either set all of those keymaps immediately or convert them into lazy's keys format to be lazy loaded, and then I just refer to the file every time I want to setup keymaps

I do group LSP + neodev + mason into a group of plugins and have a single config for all of them but that's for a combination of readability and because they need to be set up in some order.