Vim FTW
(Neo)Vim often seems daunting for people to start to work on.
The basic out of the box experience with Vim isn’t very vi improved
I’m afraid.
But then they see me vim’in, they cravin'
Being one of the cool kids with vim, I’m often asked how people can get started with vim without all the classic exiting vim memes.
A new hope arises
Recently, I had a chad at work ask me to get him started with vim!
YAAY a new incoming convert I thought!
Initial attempt
Having that my dotFiles can be ahem a bit over-engineered, I naively told him to try the following route:
- Add a vim bindings plugin to his VsCode
- Install SpaceVim for a quickstart
- Get used to stuff
- Roll his own config like a boss
The first step was fine, then we got to SpaceVim.
My days, after he showed me it (and it took a couple of seconds to load), I was instantly regretful of my actions.
I admit that I might be extremely opinionated about my vim defaults, but this experience with SpaceVim caused the exact opposite of what I wanted to achieve!
To be frank (I’d have to change my name), it backfired and the chad postponed his vim enlightenment!
THE HORROR!!1
So, going forward, I’m creating a simple 4 STEPS TO SUCCESS LADDER for on-boarding vim’ers:
- Vim bindings in whatever blasphemy they call IDE
- Vimium
- UBER simple native vim configuration (just syntax highlight and spell check for git commits and markdown):
|
|
- Basic NeoVim config which allows simple code navigation and completion
|
|