Member-only story

How to turn VSCode into Neovim šŸ™ƒ

Tom Deneire
8 min readNov 29, 2023
Photo by Klim Musalimov on Unsplash

VSCode != Neovim

Okay, first things first: of course, this post is as much a joke as anything else. VSCode is not Neovim and neither should it be! Both editors have different strengths and Iā€™m a firm believer in picking your development tools based on your specific needs. For some, that might be VSCode or a JetBrains IDE, for others that might be Neovim with Tmux.

Even though I belong to the latter category, I do fire up VSCode once in a while, specifically in scenarios where itā€™s just better than Neovim. One example is when I need to edit and run Jupyter Notebook files, which is not possible (or very impractical) in a terminal based environment. Another is that, while I have debuggers set up in Neovim, debugging is one case where using a mouse-driven interface is often quicker than keyboard shortcuts.

Moreover, even if thereā€™s probably no way to beat Neovim as a ā€œhyperextensibleā€ editor (you can literally program it to do pretty much anything), VSCode has a ton of features and a very active extension ecosystem too, so thereā€™s probably more configuration possible than some might give it credit for!

All of this got me interested lately in a little experiment: I wanted to see just how far I could get in trying to get VSCode to behave like my Neovim installation.

Create an account to read the full story.

The author made this story available to Medium members only.
If youā€™re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Tom Deneire
Tom Deneire

Written by Tom Deneire

Software engineer, technical writer, IT burnout coach @ https://tomdeneire.be/confident_coding

No responses yet

What are your thoughts?