Blink overrides existing insert-mode bindings

[julienvincent]

I'm just raising my comment from #20 into a new issue for better tracking.

As of ecb3510 blink now replaces insert-mode keybindings in the buffer even when it isn't active / currently completing.

An example of why this causes a problem is that this breaks map_cr = true behaviour from nvim-autopairs:

When I am editing with nvim-autopairs I expect the following behaviour:

fn main() {|}
// Press <Cr>
fn main() {
  |
}

But this is broken with the following blink config:

require("blink.cmp").setup({
  keymap = {
    accept = { "<Cr>" },
  },
})

Ideally we can find a way to both allow <Cr> to accept without swallowing existing <Cr> mappings on the buffer.

This behaviour pairing works fine on nvim-cmp, so it should at least be possible.

---

P.S Awesome plugin btw, sorry for making so much noise :)

[Saghen]

sorry for making so much noise :)

Don't be! You've been super helpful

[julienvincent]

It works! Thanks!

[benfrain]

First time blink user so possibly I'm doing something wrong here but I still seem to see this same issue.

If I enter <CR> here: const operator () => {|} nothing happens. In fact, pressing anywhere in Insert mode does nothing.

My config:

  {
    "saghen/blink.cmp",
    lazy = false, -- lazy loading handled internally
    -- optional: provides snippets for the snippet source
    dependencies = "rafamadriz/friendly-snippets",

    -- use a release tag to download pre-built binaries
    version = "v0.5.0",
    opts = {
      keymap = {
        ["<CR>"] = { "select_and_accept" },
      },
      highlight = {
        use_nvim_cmp_as_default = true,
      },
      nerd_font_variant = "normal",
      accept = { auto_brackets = { enabled = true } },
      trigger = { signature_help = { enabled = true } },
    },
  },

Is there anything obvious I have wrong here?

[Saghen]

You're missing the "fallback" command after your "select_and_accept"