Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

The problem with working out SnipMate under Pathogen is basically in adding new snippets, or a separate snippet bundle under the /bundles directory.

Any ideas regarding a working configuration of this problem?

share|improve this question
1  
I use ~/.vim/bundle/snipMate/snippets/ and works fine. –  Eelvex Mar 2 '11 at 9:26
1  
Same as Eelvex, all the custom snippets I've added work very well. And are you sure you want to add all of scrooloose's snippets? A little bit of copypasta may be enough. –  romainl Mar 2 '11 at 12:49
1  
Thanks guys. Problem is, I store bundles as Git repositories (submodules), and I don't want to "contaminate" the repos with untracked files. What do I do? –  Konzepz Mar 2 '11 at 21:31
    
@romainl: how did you add your custom snippets? –  Neil G Apr 15 '11 at 2:31
1  
@Neil G Then the ~/.vim/snippets/cpp.snippets road seems to be the best: you won't have conflicts when updating your bundles. Another way would be to explicitly git ignore the files you have edited. –  romainl Apr 16 '11 at 9:52

2 Answers 2

By default snipMate looks for snippets in ~/.vim/snippets so just put your new snippets files there or change the g:snippets_dir variable in Vim to any directory you want.

I have let g:snippets_dir = "~/.vim/snippets" in my vimrc file so snipMate only looks at my custom snippets files. If you want both then just use the defaults + the ~/.vim/snippets directory.

share|improve this answer

For pathogen, you can simple use git and add a submodule liket his:

 git submodule add https://github.com/garbas/vim-snipmate ~/.vim/bundle/snipmate

Check out garab's vim-snipmate github.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.