L3MON4D3

I'd also +1 the choiceNodes. It's possible to imitate ultisnips behaviour for nested placeholder with [this](https://github.com/L3MON4D3/LuaSnip/wiki/Nice-Configs#imitate-vscodes-behaviour-for-nested-placeholders) (although it might not work anymore, been a while since I tried it last...

Ah, `load_ft_func` is exclusively used by the loaders, for your purposes `ls.ft_extend("NeogitCommitMessage", {"gitcommit"})` should do it. `load_ft_func` is useful when files need to expand snippets from filetypes different from their...

Ah, that's what `ft_func` is responsible for that: ```lua ls.setup({ ft_func = require("luasnip.extras.filetype_functions").from_pos_or_filetype, load_ft_func = require("luasnip.extras.filetype_functions").extend_load_ft({ markdown = {"lua", "json"} }) }) ```

Oh, it should only expand lua-snippet when inside a fenced code-block for lua (eg. only expand snippets of the filetype treesitter reports for the current cursor-position), does that work?

Ouh, looks like the markdown-parser is a tad unreliable when it comes to reporting the correct filetype :| `get_snippet_filetypes` is used internally to get the active filetypes at the cursor-position,...

Weird, which parser do you use? I'm using just `markdown`, not `markdown_inline`

Huh. Which nvim-version are you on? I'm on master

Mhm, okay no difference there. That was my last guess, no idea what's different then :/

Could you try if injected filetypes are recognized in other circumstances? For example, `vim.cmd` in lua-files (depends on the lua-parser though, so you might have to add it)

Mmmmmm that's very weird, it looks like the highlight is even correct. `from_pos_or_filetype` is defined in [this](https://github.com/L3MON4D3/LuaSnip/blob/b840140039065e9a010c4bc50ec5a3537672a906/lua/luasnip/extras/filetype_functions.lua#L1) file, you could insert some `prints` to find what's going wrong. Maybe one...