TextMate VS Vim

I mostly work on MacOS these days and previously my general purpose text editor wax Textmate: https://github.com/textmate/textmate

Last official release was 2021, so I looked for something more regularely updated, and found CudaText. Definitely very Sublime-ish, and I like it so far.

Textmate 2.0 got open-sourced https://github.com/textmate/textmate but it looks pretty much abandoned/finished.

If you want something like TextMate maybe use TextMate? https://macromates.com

Use a native editor. VS Code is IMHO awful. Someone mentioned Sublime which is fast and has some nice features, but its non-native UI is IMHO ugly and clumsy. You might like it for similarity to VS Code, I guess. If you want something much more "Mac", though: https://macromates.com

I know no one talks about it anymore but TextMate 2 is still actively being developed and I find it excellent.

https://macromates.com/

TextMate is a well-known code editor for developers who code on a Mac system.

See, VSCode itself utilizes grammar files called “tmLanguage” files to tokenize your code. This tokenizer is borrowed from TextMate.

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