How to use the same snippets for different filetypes? about vim-vsnip HOT 18 CLOSED

Currently, vsnip does not support it.

My random thought is it would be good to provide g:vsnip_filetypes variable.

let g:vsnip_filetypes = {}
let g:vsnip_filetypes.typescriptreact = ['typescript', 'javascript']
let g:vsnip_filetypes.jinja = ['html']

from vim-vsnip.

I think vsnip's global.json is the same feature for ultisnips's all.snippets.

If these does not the same, please explain what you want.

from vim-vsnip.

Implemented in #89

from vim-vsnip.

Unfortunately this breaks the Vim way to handle sub filetypes.
In vim you would typically solve this by setting the filetype to jinja.html.

This is also the way how UltiSnips handles this.
Using filetypes with a . to separate them is supported by many other plugins as well.

Vim does this for ftplugins the same way.
Assuming you have ftplugin/jinja.vim and ftplugin/html.vim in your &rtp, vim would first source ftplugin/html.vim and then ftplugin/jinja.vim.

from vim-vsnip.

This would let the user decide if the default behavior is wanted (by not doing anything) or overwrite it with their own logic.

Somewhere here:

from vim-vsnip.

(I am not a native English speaker so every naming is hard and worry to decision...)

from vim-vsnip.

I think this is a good idea 👍

from vim-vsnip.

Another question, is there is something similar to all.snippets in UltiSnips in vsnip? can this be fixed by the above solution?

For example

let g:vsnip_filetypes = {}
let g:vsnip_filetypes['*']= ['all']

from vim-vsnip.

Working great, thanks @hrsh7th!

from vim-vsnip.

I intentionally deleted it, but I think it's OK to restore it.

For example, javascript.tsx case, how we should handle it?

1. filetypes=javascript.tsx, javascript, tsx and g:vsnip_filetypes['javascript.tsx']
2. filetypes=javascript, tsx and g:vsnip_filetypes['javascript.tsx']
3. filetypes=javascript, tsx and g:vsnip_filetypes['javascript'] + g:vsnip_filetypes['tsx']

from vim-vsnip.

Using the "Vim-logic" it would check in javascript.json and tsx.json.
When the prefix is available in both, the javascript one is used, as it is the first filetype.

from vim-vsnip.

Due to my previous decision, probably we can not able to ignorejavascript.tsx.json... sorry.

But thank you! your opinion seems correct to me.

I restore it as javascript.tsx, javascript, tsx and g:vsnip_filetypes['javascript.tsx'].

from vim-vsnip.

Hm... How to change this behavior with keeping backward compatibility.

from vim-vsnip.

What if this would prefill g:vsnip_filetypes['javascript.tsx'] = ['javascript', 'tsx']?
Of course only if the key does not exist.

from vim-vsnip.

Ah. sorry.
I was misunderstanding the previous behavior.

I was checked VsnipOpen command after set filetype=javascript.jsx in old vsnip.
Then, vsnip display javascript or jsx or global.

So we has no problem maybe.

from vim-vsnip.

I think https://github.com/hrsh7th/vim-vsnip/pull/96/files solves this problem.

from vim-vsnip.

Looks good 👍

from vim-vsnip.

Thank you!

from vim-vsnip.