13 ms·

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 a

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 https://github.com/SirVer/ultisnips [2] http://fueledbylemons.com/blog/2011/07/27/why-ultisnips/ http://fueledbylemons.com/blog/2011/07/27/why-ultisnips/

matthiasv 14y ago
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 https://github.com/Shougo/neocomplcache
- tdfx 14y ago
  Just switched to neocomplcache from AutoComplPop. Enjoying it very much so far.
gaving 14y ago
+1 for ultisnips, definitely the superior option when it comes to templating.
- davidp 14y ago
  Can you elaborate?
- don_draper 14y ago
  I just installed it. It's pretty good. The docs aren't great though. I hate sitting through screencasts.
rbonvall 14y ago
While the original author has abandoned snipmate, there is a fork that is actively maintained: https://github.com/garbas/vim-snipmate 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 14y ago
I do OK with macros which use registers: http://stackoverflow.com/questions/8120486/how-to-provide-parameter-in-vim-macro http://stackoverflow.com/questions/8120486/how-to-provide-pa...
johncoltrane 14y ago
Because UltiSnips was buggy as hell when I tried. Because the old SnipMate still works very well. Thanks.

matthiasv 14y ago

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 https://github.com/Shougo/neocomplcache

tdfx 14y ago
Just switched to neocomplcache from AutoComplPop. Enjoying it very much so far.

gaving 14y ago

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

davidp 14y ago
Can you elaborate?
don_draper 14y ago
I just installed it. It's pretty good. The docs aren't great though. I hate sitting through screencasts.

rbonvall 14y ago

While the original author has abandoned snipmate, there is a fork that is actively maintained: https://github.com/garbas/vim-snipmate 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 14y ago

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

johncoltrane 14y ago

Because UltiSnips was buggy as hell when I tried. Because the old SnipMate still works very well. Thanks.