Shift-enter mappings being ignored

[cameron1024]

Make sure you have done the following

• I have updated to the latest version of blink.cmp
• I have read the README

Bug Description

Firstly, thanks for the awesome plugin!

Apologies in advance if I've misunderstood the way keybinds are managed. I've found that, in certain files (in particular markdown and typst, but possibly others), the completion window appears after typing common punctuation characters, and so I'd like to be able to press shift+enter to dismiss the window and enter a newline.

But with the configuration I have below, shift+enter behaves exactly the same as just enter by itself (i.e. it accepts the suggestion). Is there a different approach I should be using?

Thanks 😁

Relevant configuration

{
    keymap = {
      preset = "enter",
      ['<Tab>'] = { "select_next", "fallback" },
      ['<S-Tab>'] = { "select_prev", "fallback" },
      ['<C-j>'] = { "select_next", "fallback" },
      ['<C-k>'] = { "select_prev", "fallback" },
      ['<C-c>'] = { "hide", "fallback" },
      ['<S-CR>'] = { "fallback" },
    },
    // ...
  }

neovim version

NVIM v0.11.0-dev Build type: Release LuaJIT 2.1.1713773202 Run "nvim -V1 -v" for more info

blink.cmp version: branch, tag, or commit

v0.5.1

[Saghen]

Thanks for the kind words! :) Do you mind retesting this on the latest release (v0.6.1 as of writing), and if the bug persists, trying on neovim 0.10? The outputs of :imap <CR> and :imap <S-CR> would also be helpful

I've found that, in certain files (in particular markdown and typst, but possibly others), the completion window appears after typing common punctuation characters

The window triggers due to trigger_characters, provided by the sources. We don't currently support blocking per filetype, but I've just opened an issue for that: #372

[Saghen]

Closing since this seems likely be an issue with your config but lmk if you're still running into this on a fresh config

[cameron1024]

Sorry, just got back to this - I realised the whole issue was actually a tmux issue - when I was checking to see kitty could actually handle <S-CR>, I was checking in a terminal window that wasn't running tmux, but was testing blink inside tmux, which was stopping the keybinding from working at all. The filetype-specific trigger characters seems like a very useful change in the meantime though 😁 Thanks for your effort