info.vim VS Vim

As for writing plugins though, Lua beats Vim script any time of the day. I wrote info.vim back in the early days and it was a major pain to write in Vim script. If I had to redo it today I would 100% write it in Lua.

Yeah, mapping a function instead of a mapping is even better. I just don't like if a predefined mapping is hard to remember or (even worse) conflicts with one of my existing mappings. Personally I like it the way Neovim's LSP client does it: you get a Lua (or Vim script) API that you can map yourself. In my info.vim I provide the commands :InfoNext, :InfoPrev and :InfoUp, but I also have a code snippet of reasonable default bindings in my README that people can just copy-past into their configuration. If they disagree with my defaults they can then change that snippet instead of having to fight my plugin to scrub away the defaults.

info.vim (my own)

I think we're all aware of the Man plugin, What I really want is info.vim being distributed by default aswell.

A wiki is not adequate documentation and I hate this trend of making documentation HTML only. Not everyone uses or even can use a web browser. GNU software has this great tool called Texinfo which lets you write a proper book-sized documentation with proper table of contents, chapters, and indexes. You can generate HTML, PDF, and most importantly info files. You can read info files in your terminal, in Emacs, or even in Vim (wrote a plugin for that).

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