[Zoophy]

I wish I spent the time trying to learn vIm learning something which is actually productive instead of hoping to have a better editing/writing flow with some deprecated, obscure CLI editor with a way too steep learning curve.

[danneu]

I learned Vim because the internet went out one day and I finally decided to check out `$ vimtutor`.

15 minutes later after learning commands like A, I, o, O, dd, p, and P it was clear to me that I wanted to use Vim seriously.

The hard part was arriving at a workflow, a set of plugins that I actually liked using. I imagine a great deal of people don't get to that point. I almost didn't. Especially since the commonly recommended plugins like NERDTree are awkward and clunky.

I think discovering CtrlP was the turning point for me.

A lot of luck was definitely involved. Sometimes I stay up at night wondering just how many versions of myself had given up on Vim when my wavefunction collapsed and I happened to be the chosen eigenstate that stuck with it.

[RegEx]

CtrlP is the only plugin I use. It's really great.

[sprobertson]

Learning Vim isn't that hard - it does take a few days of study to learn the core idioms of movement and manipulation, but once you wrap your head around it the rest is just practice and building muscle memory.

As far as "actually productive," having a better editing/writing flow is one of the biggest productivity enhancements I've encountered in my programming career.