Dev In The Mountain Header
A Developer In The mountains having fun

Back to Vim

I have always used vim a little bit but until recently I never took the time to really learn it, just enough to get by when I needed to. In the early days I started to know Vim and Emacs but then quickly started using full IDEs like Eclipse or various JetBrains products and really didn't look back to the basics. I pulled away from full IDEs when editors like Atom, seeing that it had all the features I really used dailly and they were quicker to get started with new projects and less resource heavy as well. After switching a few times and trying a few diffrent Editors I ended up on VS Code, it ran well, had good defaults but was easy to extend with themes and plugins and maybe the most important of all it had good and easy ability to live share code allowing me to easily flip over and see issues my team was having and help them out and get back to what I was working on quickly.

All this time I used Vim off and on but mostly just for quick changes to remote systems. I knew it had a lot more power then I waas using and occationally would try and use it but quickly switched back to VS Code for my real work as it was comfertable. I would run across articles once in a while saying you could use VIM commands on VS Code but i never really gave it a thought as I had just figured I would lose all my normal VS CODE keybindings when I did that. Then one day while looking for and easy way to select everything between quotes I again came across mention of VIM plugin; This time I figured I would give it a chance after all its just a plugin so I could aways remove it. That is when my editing world changed, I didn't lose any of the VS Code keybindings I had, and I gained all (most) that VIM had to offer too, the only little thing was that I would have to go into insert mode (i key) before I could start typing or acting like "normal" VS Code, not a big deal so I kept the plugin.

Each day I would get annoyied at some little thing I figured could be easier, but instead of looking for a VS Code plugin I would first see if it was something in VIM, it almost always was easily accomplished with a series of VIM commands. I quickly found that learning just a few new things in VIM each day was easy and also allowed me to get more comfertable with the commands I already knew as I repeated most of them sevral times a day.

now I find myself anouther convert and touting how great VS Code is with the VIM plugin, I now mostly use the standard VIM commands to navigate and make changes but enjoy the feel and looks of VS Code still.

The notes I have on here are the accumulation of notes I took while getting up to speed with VIM, they are far from compleate but should allow you to easily find most of what you would want to use in one easy place.

More places to find me
Mental Health
follow me on Mastodon