Custom Markdown Snippets Not Loading in LuaSnip

[adimail]

After adding custom Markdown snippets in the ~/.config/nvim/lua/snippets/markdown.lua file and configuring LuaSnip, the snippets are not recognized in .md files. I have ensured filetype detection works and keybindings for snippet expansion are set up. However, the snippets remain inaccessible when editing Markdown files.

snippets/markdown.md

lua/snippets/markdown.md
local ls = require('luasnip')
local s = ls.snippet
local t = ls.text_node
local i = ls.insert_node
local f = ls.function_node

return {
    -- Headings
    s('h1', { t('# '), i(1, 'Header 1') }),
    s('h2', { t('## '), i(1, 'Header 2') }),
    ...
    ...
    ...
}

Other extensions are working fine, but the markdown snippets are not working.

[adimail]

for more reference, here is my nvim config.

[olivervogel]

I have the same problem. Strangely, it only occurs with markdown files, although neovim recognizes the “markdown” filetype correctly.

require("luasnip.loaders.from_lua").lazy_load({ 
    paths = { "~/.config/nvim/lua/snippets" }
})

All snippets in other filetypes are loaded correctly.

[MrBong81]

I have the same issue using rmd files. I get vscode snippets to work just fine, but not the markdown ones.

[L3MON4D3]

Mhmm, may have to do with treesitter, IIRC they had weird names for their markdown-filetype.
What does :lua =require("luasnip").get_snippet_filetypes() print?

[olivervogel]

hat does :lua =require("luasnip").get_snippet_filetypes() print?

For me it is: { "markdown", "all" }

[L3MON4D3]

Okay, that should work then... Would you share/check your log?
Add require("luasnip").log.set_loglevel("info") before any call to load, and use require("luasnip").log.open() to view it, there should be a few lines that refer to your markdown.md-file, or at least to the path of the snippet-collection it belongs to

[olivervogel]

Thanks for your help. Here are the contents of the log file, when I open a markdown file with logging enabled:

nvim readme.md

INFO  | lua-loader: Found roots `{ "~/.dotfiles/nvim/lua/snippets" }` for paths `{ "~/.config/nvim/lua/snippets" }`.
INFO  | lua-loader: Determined roots `{}` for lazy_paths `{}`.
INFO  | tree-watcher: Monitoring root-directory ~/.dotfiles/nvim/lua/snippets with autocmd-monitor.
INFO  | lua-loader: Registering lazy-load-snippets for ft `all` from file `~/.dotfiles/nvim/lua/snippets/all.lua`
INFO  | lua-loader: Registering lazy-load-snippets for ft `html` from file `~/.dotfiles/nvim/lua/snippets/html.lua`
INFO  | lua-loader: Registering lazy-load-snippets for ft `javascript` from file `~/.dotfiles/nvim/lua/snippets/javascript.lua`
INFO  | lua-loader: Registering lazy-load-snippets for ft `lua` from file `~/.dotfiles/nvim/lua/snippets/lua.lua`
INFO  | lua-loader: Registering lazy-load-snippets for ft `markdown` from file `~/.dotfiles/nvim/lua/snippets/markdown.lua`
INFO  | lua-loader: Registering lazy-load-snippets for ft `php` from file `~/.dotfiles/nvim/lua/snippets/php.lua`
INFO  | lua-loader: Registering lazy-load-snippets for ft `sh` from file `~/.dotfiles/nvim/lua/snippets/sh.lua`
INFO  | lua-loader: Registering lazy-load-snippets for ft `vue` from file `~/.dotfiles/nvim/lua/snippets/vue.lua`
INFO  | lua-loader: Initialized snippet-collection at `~/.dotfiles/nvim/lua/snippets`
INFO  | lua-loader: Loading lazy-load-snippets for filetype ``
INFO  | lua-loader: Loading lazy-load-snippets for filetype `all`
INFO  | lua-loader: Adding snippets for filetype `all` from file `~/.dotfiles/nvim/lua/snippets/all.lua`
INFO  | loaders: Adding 3 snippets and 0 autosnippets from ~/.dotfiles/nvim/lua/snippets/all.lua to ft `all`
INFO  | lua-loader: Loading lazy-load-snippets for filetype `markdown`
INFO  | lua-loader: Adding snippets for filetype `markdown` from file `~/.dotfiles/nvim/lua/snippets/markdown.lua`
INFO  | loaders: Adding 4 snippets and 0 autosnippets from ~/.dotfiles/nvim/lua/snippets/markdown.lua to ft `markdown`
INFO  | snipmate-loader: Loading lazy-load-snippets for filetype `markdown`
INFO  | vscode-loader: Loading lazy-load-snippets for filetype `markdown`
INFO  | lua-loader: Loading lazy-load-snippets for filetype `all`
INFO  | snipmate-loader: Loading lazy-load-snippets for filetype `all`
INFO  | vscode-loader: Loading lazy-load-snippets for filetype `all`

It looks to me as if everything is working according to plan.

• Snippet files are recognized and loaded
• The number of snippets is correct

However, when I want to trigger a snippet in the Markdown file, nothing happens. I use <tab> as trigger. This is how I have currently configured it:

   keys = {
      { "<tab>", function()
         if require("luasnip").expand_or_jumpable() then
            require("luasnip").expand_or_jump()
         else
            -- press tab key
            vim.api.nvim_feedkeys(
            vim.api.nvim_replace_termcodes("<Tab>", true, true, true), "n", true)
         end
      end, mode = "i", silent = true },

      { "<tab>", function()
         require("luasnip").jump(1)
      end, mode = "s", noremap = true, silent = true },

      { "<s-tab>", function()
         require("luasnip").jump(-1)
      end, mode = "s", noremap = true, silent = true },
   }

It should be noted that I can trigger snippets from all.lua in the Markdown file, only the Markdown-specific snippets are not triggered, but output a regular tab.

[L3MON4D3]

Well, color me confounded o.O

What does :LuaSnipListAvailable print?

[olivervogel]

What does :LuaSnipListAvailable print?

This also looks correct. My snippets for all and markdown are listed here.

An excerpt:

{
  all = { {
    { 
      description = { "lorem" },
      name = "lorem",
      regTrig = false, 
      trigger = "lorem",
      wordTrig = tr
    },

    [...]

  markdown = { { 
    { 
      description = { "img" },
      name = "img",
      regTrig = false, 
      trigger = "img",
      wordTrig = tr
    },

    [...]

} 

[L3MON4D3]

Damn :/
I've created a branch expand_inspect, could you try to reproduce it on that branch and share the log-messages produced by it when expanding a markdown-snippet?

[L3MON4D3]

Oh, and another, simpler idea: remove the expand_or_jumpable-test, and just let the keybind call expand immediately

[olivervogel]

Oh, and another, simpler idea: remove the expand_or_jumpable-test, and just let the keybind call expand immediately

Unfortunately, this does not bring success.

I've created a branch expand_inspect, could you try to reproduce it on that branch and share the log-messages produced by it when expanding a markdown-snippet?

Sure. I have updated the installed LuaSnip version to the expand_inspect branch (commit 7ecf350).

Then I open readme.md and trigger first the snippet lorem (from all.lua) and then img (from markdown.lua).

This is the output in ~/.local/state/nvim/luasnip.log:

ERROR | 16:22:05 | temp: Matching snippet with trigger php against line lorem gives expand_params nil
ERROR | 16:22:05 | temp: Matching snippet with trigger fox against line lorem gives expand_params nil
ERROR | 16:22:05 | temp: Matching snippet with trigger lorem against line lorem gives expand_params {
      |   captures = {},
      |   trigger = "lorem"
      | }
ERROR | 16:22:05 | temp: expand called
ERROR | 16:22:05 | temp: next_expand_params{ {
      |     captures = {},
      |     trigger = "lorem"
      |   } }
ERROR | 16:22:05 | temp: se_opts{ {
      |     clear_region = {
      |       from = { 22, 0 },
      |       to = { 22, 5 }
      |     },
      |     expand_params = {
      |       captures = {},
      |       trigger = "lorem"
      |     }
      |   } }
ERROR | 16:22:08 | temp: Matching snippet with trigger php against line img gives expand_params nil
ERROR | 16:22:08 | temp: Matching snippet with trigger fox against line img gives expand_params nil
ERROR | 16:22:08 | temp: Matching snippet with trigger lorem against line img gives expand_params nil

php, fox and lorem are all snippets from all.lua.

I assume that there should also be a matching for the Markdown snippets?

[L3MON4D3]

I've pushed another log-message to the branch, could you pull and try again?

[olivervogel]

I've pushed another log-message to the branch, could you pull and try again?

Sure. Here is the output. Again I opened a markdown file and triggered the snippet lorem (from all.lua) first and then img (from markdown.lua).

ERROR | 16:16:28 | temp: fts{ { "markdown", "all" } }
ERROR | 16:16:28 | temp: fts{ { "markdown_inline", "all" } }
ERROR | 16:16:28 | temp: fts{ { "markdown_inline", "all" } }
ERROR | 16:16:28 | temp: fts{ { "markdown_inline", "all" } }
ERROR | 16:16:28 | temp: fts{ { "markdown_inline", "all" } }
ERROR | 16:16:29 | temp: fts{ { "markdown_inline", "all" } }
ERROR | 16:16:29 | temp: Matching snippet with trigger php against line lorem gives expand_params nil
ERROR | 16:16:29 | temp: Matching snippet with trigger fox against line lorem gives expand_params nil
ERROR | 16:16:29 | temp: Matching snippet with trigger lorem against line lorem gives expand_params {
      |   captures = {},
      |   trigger = "lorem"
      | }
ERROR | 16:16:29 | temp: expand called
ERROR | 16:16:29 | temp: next_expand_params{ {
      |     captures = {},
      |     trigger = "lorem"
      |   } }
ERROR | 16:16:29 | temp: se_opts{ {
      |     clear_region = {
      |       from = { 22, 0 },
      |       to = { 22, 5 }
      |     },
      |     expand_params = {
      |       captures = {},
      |       trigger = "lorem"
      |     }
      |   } }
ERROR | 16:16:31 | temp: fts{ { "markdown", "all" } }
ERROR | 16:16:31 | temp: fts{ { "markdown_inline", "all" } }
ERROR | 16:16:31 | temp: fts{ { "markdown_inline", "all" } }
ERROR | 16:16:32 | temp: fts{ { "markdown_inline", "all" } }
ERROR | 16:16:32 | temp: Matching snippet with trigger php against line img gives expand_params nil
ERROR | 16:16:32 | temp: Matching snippet with trigger fox against line img gives expand_params nil
ERROR | 16:16:32 | temp: Matching snippet with trigger lorem against line img gives expand_params nil

[L3MON4D3]

Ohhh, see there, at some points the filetype is markdown_inline!
You can do one of two things:

1. ls.filetype_extend("markdown_inline", {"markdown"}) will also look at markdown snippets when the filetype is markdown_inline
2. Add your snippets under the filetype markdown_inline.

I think you'll want to do 1., but I'm not 100% sure because markdown_inline seems more specific, and may be more appropriate.. When does it show markdown_inline?