paint-brush
Transitioning From VSCode to NeoVimby@maksimmuravev
4,436 reads
4,436 reads

Transitioning From VSCode to NeoVim

by Maksim Muravev2mFebruary 3rd, 2023
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

As a DevOps engineer, I recently reached a significant milestone: I switched code editors for the fifth time in my career. When I first began writing code, I quickly settled on using Vim. Despite its reputation for being fast and efficient, what drew me to Vim was the endless possibilities for customization through plugins, abbreviations, hotkeys, and scripts. As a result, I spent significant time customizing my setup.
featured image - Transitioning From VSCode to NeoVim
Maksim Muravev HackerNoon profile picture
Maksim Muravev

Maksim Muravev

@maksimmuravev

DevOps Engineer.

0-item

STORY’S CREDIBILITY

Original Reporting

Original Reporting

This story contains new, firsthand information uncovered by the writer.

L O A D I N G
. . . comments & more!

About Author

Maksim Muravev HackerNoon profile picture
Maksim Muravev@maksimmuravev
DevOps Engineer.

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite