:set filetype=html gg=G Was I not supposed to get exactly what I wanted? http://i.imgur.com/P6YLdRA.png http://i.imgur.com/P6YLdRA.png I do use the menti

:set filetype=html gg=G Was I not supposed to get exactly what I wanted? http://i.imgur.com/P6YLdRA.png http://i.imgur.com/P6YLdRA.png I do use the mentioned javascript-vim plugin. However, majority of the plugins I install are because I'm simply one short "Bundle 'user/repo'" away from trying out something I may choose to use. If I was to purposely cut down my number plugins, I probably would only keep minibufexpl and language specfics. The most important vim plugins are those that are simply improvements of basic vim functionality that are more aware of language specifics (i.e. javascript-vim, erlvim). Plugins like NERDTree look nice, but do I actually use them in practice? Not really. I barely use even use ctrl+p: most of the time using :e and tabbing my way to victory is quick enough to be a moot point. There are costs and benefits to using any editor. I've spent a large amount of my life ssh'd into remote boxes from a Windows machine. It was pretty natural for me to pick up the most common and still powerful command line editor available. I was born into a generation of kids more comfortable using 'WASD' than walking around in real life; it wasn't difficult to get used to hjkl quickly. I don't really consider there to be a learning curve more than 'it isn't obvious how to do things unless you read documentation first' which is actually to be expected. Most of us won't work with a programming language until we've read a book on it and sufficiently experimented on our own. Programming languages are a tool. A text editor is a tool. A similar learning curve seems fair to me.