On Jul 11, 2011, at 4:42 AM, Andrew Stewart wrote: > I tried VimBalls a while ago but grew frustrated at the work that needs doing > when a script/plugin isn't already packaged as a VimBall. I switched to > Pathogen and it has always worked wonderfully. If a conflict with > VimOutliner is the only thing holding you back, I'd file bug reports with the > authors of VimOutliner and Pathogen and hope it'll be resolved soon.
Thanks, Andrew. That was my question about the vimball approach. David makes the solution sound relatively simple, though I imagine that if I were to get down to work with it I would have more questions. VAM appeals for the same reasons as Pathogen plus others, e.g., automatic fetching and resolving of dependencies. I am not using VimOutliner at the moment, so the apparent conflict with at least Pathogen is not an issue. > Finally, if you are familiar with a version control system, I'd suggest > version-controlling your home Vim directory regardless of what system you use > to wrangle plugins. Thanks for this suggestion. I take it git would be a way to do that. I understand it is not difficult to install, but actively using it would probably be a bit more of a challenge for me. I'm gonna hold off for the moment. Sincerely, ------------------------------------------------------------------------------------------ Eric Weir Decatur, GA USA eew...@bellsouth.net -- You received this message from the "vim_mac" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
