How to reliably set keymaps when loading LuaSnip via Lazy.nvim

[goerz]

I have the following in ~/.config/nvim/lua/custom/plugins/luasnippets.lua:

return {
  {

    "L3MON4D3/LuaSnip",
    version = "2.3.0",
    config = function()

      local ls = require("luasnip")
      local types = require("luasnip.util.types")
      ls.setup({
        keep_roots = true,
        link_roots = true,
        link_children = true,
        update_events = "TextChanged,TextChangedI",
        delete_check_events = "TextChanged",
        ext_opts = {
          [types.choiceNode] = {
            active = {
              virt_text = { { "choiceNode", "Comment" } },
            },
          },
        },
        -- treesitter-hl has 100, use something higher (default is 200).
        ext_base_prio = 300,
        -- minimal increase in priority.
        ext_prio_increase = 1,
        enable_autosnippets = false,
      })

      -- "Select mode" is what luasnip ends up in when snippets contain placeholder text
      vim.keymap.set({ "i", "s" }, "<C-K>",
        function()
          if ls.expand_or_locally_jumpable() then
            ls.expand_or_jump()
          end
        end,
        { desc = "Expand or jump forward in lua-snippet", silent = true })

      vim.keymap.set({ "i", "s" }, "<C-J>", function()
        if ls.jumpable(-1) then
          ls.jump(-1)
        end
      end, { desc = "Jump backward in lua-snippet", silent = true })

      vim.keymap.set({ "i", "s" }, "<C-B>", function()
        if ls.jumpable(-1) then
          ls.jump(-1)
        end
      end, { desc = "Jump backward in lua-snippet", silent = true })

      vim.keymap.set({"i", "s"}, "<C-E>", function()
        if ls.choice_active() then
          ls.change_choice(1)
        end
      end, { desc = "Switch between choices in lua-snippet", silent = true})

      require("luasnip.loaders.from_lua").load() -- load from ~/.config/nvim/luasnippets

    end,  -- config

  },
}

Based on my snippets in ~/.config/nvim/luasnippets/all.lua, I should be able to open nvim, go into insert mode, type hi<ctrl-k> and have that expand to "Hello, world!". That only works a fraction of the time. It seems that the keymaps do not get set every time I open vim, but only sporadically. Maybe there is some other plugin that sets a <C-K> keymap and there is some kind of "race condition" between them, with the lazy loading. But I can't find anything in my configuration that would be an obvious conflict.

I have a Telescope viewer for keymaps, and that shows the correct i ▏<C-K> ▏Expand or jump forward in lua-snippet (matching the description I've set in the config) when the shortcut works, but i ▏<C-K> ▏<anonymous> when it doesn't. But even when it doesn't, if I do :verbose map <C-K>, I still get

s  <C-K>       * <Lua 107: ~/.config/nvim/lua/custom/plugins/luasnippets.lua:32>
                 Expand or jump forward in lua-snippet

So I can't tell what else might have defined the <C-K> keymap somewhere, based on that.

What is the correct and reliable way to set the keymaps for LuaSnip in a Layz.nvim setup?

Further updates:

• If I disable LuaSnip, :verbose map <C-K> shows C-K as unmapped.
• When C-K fails to work after starting vim, :Lazy reload LuaSnip makes it work. Of course, I don't want to manually have to reload plugins all the time

[goerz]

Okay, figured it out. First, I didn't realize that :verbose map <C-K> does not include Input-mode mapping (only Normal, Visual, Select, Operator-pending). So, the appropriate command is :verbose imap <C-K and that revealed a conflict with the emacs-bindings.nvim plugin, which I had forgotten about.

Restricting emacs-bindings.nvim to command mode solved the problem.