[intractable]

Every time an article like this comes up, snipMate seems to be mentioned. This particular author even pointed to the old repository which appears unmaintained and has not had a check-in for two years.

Where's the love for UltiSnips? [1]

UltiSnips is actively maintained and well documented, not to mention supporting many more features, such as Python interpolation. More info at [2].

[1] https://github.com/SirVer/ultisnips

[2] http://fueledbylemons.com/blog/2011/07/27/why-ultisnips/

[matthiasv]

Actually, where's the love for neocomplcache? [1]

neocomplcache is actively maintained and well documented, not to mention supporting many more features, such as file path completion, register completion, omni completion and Vim completion.

[1] https://github.com/Shougo/neocomplcache

[tdfx]

Just switched to neocomplcache from AutoComplPop. Enjoying it very much so far.

[rbonvall]

While the original author has abandoned snipmate, there is a fork that is actively maintained: https://github.com/garbas/vim-snipmate

I've been a happy user of snipmate, but I'll give ultisnips a try. Thanks for the tip!

[rektide]

I do OK with macros which use registers: http://stackoverflow.com/questions/8120486/how-to-provide-pa...

[gaving]

+1 for ultisnips, definitely the superior option when it comes to templating.

[don_draper]

I just installed it. It's pretty good. The docs aren't great though. I hate sitting through screencasts.

[davidp]

Can you elaborate?

[johncoltrane]

Because UltiSnips was buggy as hell when I tried.

Because the old SnipMate still works very well. Thanks.