[midgetjones]

It's totally worth it.

For me, I learned vim & touch typing at the same time. Generally I learned while doing side projects, supplemented with general vim sessions (such as the built-in tutor, and http://vim-adventures.com/).

Many find it easier to start off with GUI vim as your favourite keyboard shortcuts are still there, but I found that too much of a crutch. Once you commit a few standard sets of motions to muscle memory, I don't think you'll find that much holds you back in day-to-day typing. If you notice yourself doing something repetitive when editing, go and look up how to do that thing more elegantly, and carry on.

I'd also just ignore all the customisations until you find yourself at least somewhat productive with the 'factory settings'.

[midgetjones]

Oh, and for typing: https://www.gnu.org/software/gtypist/

No other tutor stuck for me.

[tdb7893]

Can you add code completion or basic static analysis to vim? I've found it fine for editing but it lacks the information of the IDEs that I generally use

[pfranz]

I've had trouble with the completion plugins for Vim. There'd be a "completion engine" that needed a language-specific "plugin" and I had trouble getting those + dependencies working in various environments (or they'd suck down CPU resources). Maybe if I just set it up once in one place it'd work fine. It might just be me since the CPU resource suck bothers me in other IDEs like PyCharm.

I really like the out of the box completion vim has where it completes against words in files you have open. Most of the completion I need is long variable names or functions/modules and if it's not in the same file I'm editing I already had it open in another buffer.

That and a basic PEP8 linter work just as well for me as any of the major IDEs I've used.

[JupiterMoon]

https://github.com/Valloric/YouCompleteMe