local_vimrc VS Vim

Other approaches are available as well. For instance, autocommands in the .vimrc are possible as well, but every time you move around that directory you'd have to update the autocommand.

Regarding project management, .exrc is enough as long we're working on simple project where everything is in the same directory. On real project I've ended up needing and writing much, much more.

buffer wise, from a local vimrc for instance, with let b:tag_options = { 'no_auto': 0}

snake is one of the possible naming policies. Several are hard-coded: snake, UpperCamelCase, lowerCamelCase, SCREAMING_SNAKE_CASE. Other can be configured (in local vimrc plugins for instance), and then used where we can expect it to make sense: member variables, local variables, static variables, types, getter...

I'm not sure about the new plugin advertised, but 'exrc' is restricted to the current directory. Its settings won't be applied to subdirectories -- unlike to what other localvimrc plugins do

There have been six releases of Vim _this week_. So, no, Vim is not "dead".

https://github.com/vim/vim/tags

Vim

We wanted this machine to be as lean as possible. There is only so much memory and processing power to go around. Remember, our machine has 3 GHz Dual-Core Intel Core i7 processor with 16 GB 1600 MHz DDR3 memory. We also wanted as much of that space and power to be used for serving up our web applications. However, we also wanted to have an additional option for editing any code files, in addition to vim.

Vim: winget install vim.vim

So Raylib library could be your best option. Let's code, just open your text editor like vim or VSCodium in your Windows, Linux or Mac computer and let's build our indie game with Raylib library, no extra dependencies are needed.

nevermind, after a little searching, I found the solution, this isn't 'a nvchad problem or neovim problem, but a vim problem, and this github issue explains it. In the bottom of the issue, someone did post a fix here, but I haven't really tried it.

Then I went to official vim GitHub and looked around and it also had only instruction for installing vim from scratch.

When you said Vim, I thought you were talking about Vim (a code editor). Clearly not haha