Add Shougo/neosnippet-snippets. Fixes #539.

[ljani]

Shougo/neosnippet.vim version 4.1 split the repository into two and the other half is now missing. This causes following errors on Mac (#539) and Cygwin at least:

neosnippet default snippets cannot be loaded.
You must install neosnippet-snippets or disable runtime snippets.

I'm not sure why gVim (on Windows) doesn't warn about this.

This PR adds Shougo/neosnippet-snippets as we're already using the "extra" snippets, so it makes sense to include the default snippets instead of disabling them.

More info of the breaking change: Shougo/neosnippet.vim@5dba6a0

[ljani]

Meh, managed to add them in the wrong order.. I guess it doesn't make much difference, but it's nice to have proper cosmetics.

[johntyree]

In .vimrc we specify

            " Use honza's snippets.
            let g:neosnippet#snippets_directory='~/.vim/bundle/vim-snippets/snippets'

does this not handle this issue? I have no errors.

[ljani]

Honza's vim-snippets is different from neosnippet-snippets. The line you quoted, enables Honza's snippets, see Shougo/neosnippet towards the end of the page

@johntyree: What OS are you using? gvim on Windows doesn't whine either, but console vim in Cygwin throws the error.

[johntyree]

@ljani I realize it's a different set of snippets, but I thought it would handle the "default snippets" problem. Perhaps not?

I'm on OSX and Linux, but my own spf13 is heavily modified and not a good reference ;)

[ljani]

Ah, sorry, I misunderstood you. Anyway, the default snippets are loaded here (+3 lines) whereas those additional snippets are only loaded here after throwing the error.

The problem should be reproducible on OSX as well, as mentioned in #539. I guess your customizations solve the problem then.

[lukedomanski]

@ljani "I'm not sure why gVim (on Windows) doesn't warn about this"'

Unlike you, I was getting this error on Windows gVim also. These commits solved the issue for me. Though I have not checked for side effects yet.

I don't understand what you an @johntyree were referring to above, do "we" need this commit? If so, why is it sitting so long without being merged?

Cross-ref: #539