Scope not recognized? about vim-snippets HOT 8 CLOSED

Hard to say without seeing your config. Usually, problems like this are related to VundleVim/Vundle.vim#202.

from vim-snippets.

OK, I've just put my .vimrc here.
The problem you've linked to is about bad filetype recognition. But as I wrote, the autocomplete of
:set filetype=<TAB>
outputs php. Isn't that a sign that filetype recognition works?

from vim-snippets.

no, it isn't.

from vim-snippets.

Looking over your vimrc right now. Generally speaking the comment marker does only work on the beginning of the line - it sometimes also works later, but that is not guaranteed.

I also do not see UltiSnips sourced in your .vimrc.

from vim-snippets.

Thanks for hint about the comment marker.
About UltiSnips: As I wrote, I am using garbas/vim-snipmate for snippets, isn't that OK for this snippet plugin?

from vim-snippets.

Ah, sorry. Yes, you can use garbas/vim-snipmate. But I cannot give you support for that as I do not know it :). If you have python support in your vim, you can also try tracking https://github.com/sirver/ultisnips instead which I know well and can help track down problems.

from vim-snippets.

Hi @georgjaehnig! In SnipMate, when loading snippets for certain scopes, other scopes may be loaded automatically. These are called scope aliases, and SnipMate defines some by default, including a PHP -> JavaScript, HTML alias. This is all documented under the SnipMate-options helptag. If you want, you can disable the default aliases entirely by putting let g:snipMate_no_default_aliases = 1 in your vimrc.

from vim-snippets.

Thanks, this was what I was looking for!

from vim-snippets.