> Bram: I have to admit I don’t use many plugins, other than what is included with the distribution (such as matchit and termdebug). When I need something I tend to either make a quick hack or add it to the Vim base. That’s the luxury of being the creator :-).
This so much. There are amazing plugins out there, but for almost everything I really need, they are overkill. vim comes with so many things included out-of-the-box (just look at netrw), and for the few things I need on top of that, ahcking together a small function bound to a <leader>Key combo which calls an external script is usually enough.
> A Markdown acolyte came to Master Wq to demonstrate his Vim plugin.
> “See, master,” he said, “I have nearly finished the Vim macros that translate Markdown into HTML. My functions interweave, my parser is a paragon of efficiency, and the results nearly flawless. I daresay I have mastered Vimscript, and my work will validate Vim as a modern editor for the enlightened developer! Have I done rightly?”
> Master Wq read the acolyte’s code for several minutes without saying anything. Then he opened a Markdown document, and typed:
> > :%!markdown
> HTML filled the buffer instantly. The acolyte began to cry.
This so much. There are amazing plugins out there, but for almost everything I really need, they are overkill. vim comes with so many things included out-of-the-box (just look at netrw), and for the few things I need on top of that, ahcking together a small function bound to a <leader>Key combo which calls an external script is usually enough.