nvim-defaults.vim VS Vim

To make it easier, I wrote a plugin so Vim has the similar defaults to neovim. Vim finds .vim files using neovim paths (e.g. ~/.config/nvim/init.vim and ~/.local/share/nvim/site)

This plugin gives Vim the same defaults, path and directory layout as Neovim: https://github.com/mikeslattery/nvim-defaults.vim

I am keeping my config backward compatible with Vim, so I'm only using Lua for neovim-specific stuff. If packer is compelling enough, I may make a break with Vim (and instead use sshfs or nvim scp://... to edit remote server files).

Ever ssh into a server and which you had nvim and its defaults, and/or maybe the ability to use your nvim dotfiles? I wrote a plugin for that: https://github.com/mikeslattery/nvim-defaults.vim

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