dotvim VS Vim

I have a whole file full of mappings like this that let Vim recognize various special key combinations from any terminal emulator I've used in the last 20 years. It's a mess: https://github.com/mgedmin/dotvim/blob/master/plugin/keyboard-workarounds.vim

https://github.com/mgedmin/dotvim, accumulated over many years.

So, three out of four? https://github.com/mgedmin/dotvim

Assuming I understood your desire correctly? I have a function to jump to the original (or patched) file when I press Enter on a line of diff: https://github.com/mgedmin/dotvim/blob/master/ftplugin/diff.vim

I use a custom foldexpr. I've been using it for many years, and polished it to do the right thing on all the codebases I've used it on.

My ~/.vim/ is a Git repository and I make it support older versions of Vim by checking for the existence of features before using them, because I couldn't stand my .vimrc emitting any errors on Vim startup. If you're interested, it's here: https://github.com/mgedmin/dotvim/

The primary reason why I need timeout/ttimeout is to have a working Escape key, when you also want to have custom bindings for various key combinations (e.g. ctrl+shift+arrows) that aren't natively recognized for your terminal for some reason, and thus you end up creating compatibility mappings for them.

My ~/.vim is here, if you're curious about the details: https://github.com/mgedmin/dotvim/

I'm perfectly happy with ~/.vim in a separate git repository (mine), with all the plugins installed via vim-plug.

My vimrc is, uhh, big, but I've tried to keep it commented.

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