docToolchain VS Vim

An implementation of the docs-as-code approach, docToolchain is a collection of scripts that makes it easy to create and maintain powerful technical documentation. It is a popular open-source project that uses jBake under the hood as the SSG. docToolchain can publish to Confluence, generate PDF using an Asciidoctor plugin, and more.

[1] Gradle based, which is probably why it's fading a little bit. https://github.com/docToolchain/docToolchain

In addition to this, the focus will be laid on exporting data and integration with other tooling. This includes a convenience library for programmatic processing, static site export, and a set of recipes, e.g. for integrating with things like docToolchain.

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