Stray ">>>" at end of ruby.snippets about vim-snippets HOT 11 CLOSED

Fixed. Thanks for taking the time to report this.

from vim-snippets.

Hey, maybe will be a good idea to split the Ruby snippets on Ruby and Rails ones?

from vim-snippets.

@tag - Good idea. Same as Python/Django. Go for it!

from vim-snippets.

Ok! I'll split they tomorrow! :-)

from vim-snippets.

Hey @honza is it possible to load two snippets files for a file type? How is this made for Python and Django?

from vim-snippets.

Perhaps extract those for rspec also?

from vim-snippets.

@taq - thoughts on the rspec stuff? I'm not even sure what the syntax looks like.

from vim-snippets.

@honza, @thenoseman, yes, could be a good choice to split the rspec also. When using Ruby we don't need the Rails snippets, when using Rails we do need the Ruby snippets, but when using Rails we don't necessarily need the rspec snippets. :-)

from vim-snippets.

@honza, @thenoseman, seems that the Rails snippets are already there on the eruby.snippets file. So I think we can move, for example, this cfor snippet there. I'll do this and check the rSpec snippets file, maybe we need to ask vim-snipmate to load the rspec snippets together with the ruby one when the filetype is ruby or eruby.

from vim-snippets.

I don't think there is a way to import snippets from a snippets file to another snippets file - which would be awesome. There is a hacky way this can be accomplished though. There's a global variable in snipmate that will allow you to override the context per file extension. For example: you open a .rb file and both Ruby and Ruby on Rails snippets are loaded. Unfortunately, I can't remember the right syntax for this - it shouldn't be too hard to find. Have a look in the issues for snipmate.

from vim-snippets.

Hey @honza. I found that vim-snipmate allows loading another snippets based on the filetypes, check the scope_aliases on
https://github.com/garbas/vim-snipmate/blob/master/autoload/snipMate.vim
If there is really a need to split the Ruby with the rSpec snippets (btw, I'm not the correct person to keep rSpec, because I just use regular TDD), I'll ask to change the scope_aliases var to allow 'ruby','rspec'. :-)

from vim-snippets.