I don't have my dotfiles public quite yet (on my list) but here's my neovim config. It's kind of a mess of looking up others and from the docs, but it works. I've only recently moved to neovim's built-in LSP (was previously using coc.vim and ALE) so I doubt it's perfect but I haven't had any issue yet!

https://pastebin.com/2AZKJM3D

Nice coc

Get a vim distribution that makes plugin installs easy. I use vimrc, and it has instructions for where to clone plugins.

It's my default text editor now, for any language. (Vim is my backup editor for situations like sshing into a system that doesn't have Textadept installed since Vim is usually installed and if not that, at least vi is.)

My main reason for switching over to it finally was the ease in which new languages can be added to its support. I program in a lot of ... uncommon languages. Languages which lack representation in lexical coloration in editors (SNOBOL4, say, or Rexx, or Logtalk) or which, when "supported" are done so lousily it may be better not to use it at all. With Textadept I can whip up basic lexical coloration without breaking a sweat (usually under an hour barring weirdness like SNOBOL4's) and can do fancy tricks like having a separate lexer for each dialect of a language (SWI-Prolog vs. GNU Prolog, for example) without a whole lot more work. Further I can trivially handle embedded languages (like SQL embedded in C or separate the coloration of the Java and HTML components in a JSP page) and, even more fun, I can inherit lexers.

For an example of that last item, my Logtalk lexer is basically all of my Prolog lexers (complete with the dialect switches) with the Logtalk extras layered on top, so although Logtalk is a more complicated language than Prolog, lexically speaking (it's all of Prolog plus more), my Logtalk lexer is about 20% of the size of my Prolog lexer. And if I fix a mistake in my Prolog lexer, or enhance it in some way, my Logtalk lexer comes along for the ride.

I've not seen any text editor that comes close to that degree of lexical coloration support, and its support for snippets, tagging, folding, etc. is also nigh-on best of breed.

I don't feel like explaining it in depth tbh, so there's this comment thread.
https://www.reddit.com/r/learnprogramming/comments/nmliyu/comment/gzpl1k4/?utm_source=share&utm_medium=web2x&context=3
The reason why I would not call it an IDE is that it is designed as a lightweight code editor first. The build/debug environment is not integrated, you can keep things separated, which is what I like about it. If you want an integrated environment, VS code lets you integrate it yourself because it is extensible. The power you get from VS code's extensibility makes it seem like an IDE at times, but it is clearly a different beast entirely when you compare it to Visual Studio IDE.