I moved from VSCode to Emacs with the help of Doom Emacs. You can check it out online. It’s a distribution and configuration management solution.
Generally people like to recommend writing your config from scratch but that didn’t work for me.
It comes with pretty much all you requested out of the box.
One thing I liked more than with the default Emacs setup is that I could “activate” support for a Language just by un-commenting a line in the well organized config.
Ooh, thanks! That sounds like something that will help me. I tend to do better when I can get something running like someone else has done in the past, then slowly tweak things as I learn more about it. My current VSCode setup and all my dotfiles have been slowly cribbed and edited from various sources who knew more than me about those things.
Seconded, Doom Emacs is such a huge QoL improvement over the DYI solution with a basic Emacs.
(I did use the upstream vanilla Emacs, but the pain of LSP support, etc. etc. was just too much until I tried Doom Emacs... and suddenly Emacs is usable again!)
Generally people like to recommend writing your config from scratch but that didn’t work for me.
It comes with pretty much all you requested out of the box.
One thing I liked more than with the default Emacs setup is that I could “activate” support for a Language just by un-commenting a line in the well organized config.