neomutt VS Vim

https://github.com/neomutt/neomutt is a mature project with similar functionality in its arsenal via tagging and vim bindings, not limited to gmail either. You can also write emails in vim/$EDITOR fluidly.

I checked out the neomut repo and notmuch repo and unpacked ncurses 6.4

git clone https://github.com/neomutt/neomutt ./configure --notmuch --with-notmuch=/usr/local/lib/notmuch And because it gives me the error: Checking for DocBook DTDs... Error: couldn't execute "xmlcatalog": no such file or directory ... I just disable it, because I don't need a book:

I think it's always worth mentioning neomutt[1] when mutt comes up these days. Development is fairly active [2] and a lot of patches that people have been working on over the years have been merged, like the various header compression techniques, sidebar, search and unified inbox with notmuch etc.

[1] https://neomutt.org/feature

[2] https://github.com/neomutt/neomutt

based on this: https://github.com/neomutt/neomutt/issues/717

I'd also like to do a similar thing with neomutt, which will definitely have to be built from source.

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