-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Understand treesitter filetypes #1174
Comments
The fts of a parser are available on |
Can you try with this pr ? |
Works! |
Now it does not work anymore! ft_func = require('luasnip.extras.filetype_functions').from_pos_or_filetype I get
every time I try to expand a snippet. EDIT: |
Dang, I'm surprised that 1. vim.list_contains was not available before 0.10, and 2. that from_pos_or_filetype does not throw the error, it just calls from_cursor_pos. |
Treesitter uses
latex
as the filetype name instead oftex
like native vim.In #823 similarly one had to
ls.filetype_extend("markdown_inline", {"markdown"})
in order to makework.
Is it possible/useful to make Luasnip understand the treesitter names such that I don't manually need to
filetype_extend
all treesitter names to native ones?The text was updated successfully, but these errors were encountered: