Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pressing any key in insert mode quits neovim #218

Closed
2 tasks done
kryptamine opened this issue Oct 30, 2024 · 6 comments
Closed
2 tasks done

Pressing any key in insert mode quits neovim #218

kryptamine opened this issue Oct 30, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@kryptamine
Copy link

Make sure you have done the following

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

Bug Description

I've just updated to the new version, set keymap to default.
Pressing any key in insert mode quits neovim

Relevant configuration

return {
  {
    'saghen/blink.cmp',
    lazy = false,
    version = 'v0.*',
    opts = {
      keymap = 'default',
      sources = {
        providers = {
          buffer = {
            fallback_for = {},
            max_items = 4,
            min_keyword_length = 1,
            score_offset = -3,
          },
        },
      },
      highlight = {
        -- sets the fallback highlight groups to nvim-cmp's highlight groups
        -- useful for when your theme doesn't support blink.cmp
        -- will be removed in a future release, assuming themes add support
        use_nvim_cmp_as_default = false,
      },
      -- set to 'mono' for 'Nerd Font Mono' or 'normal' for 'Nerd Font'
      -- adjusts spacing to ensure icons are aligned
      nerd_font_variant = 'mono',
    },
  },
}

neovim version

v0.10.2

blink.cmp version: branch, tag, or commit

5.0.0

@kryptamine kryptamine added the bug Something isn't working label Oct 30, 2024
@Saghen
Copy link
Owner

Saghen commented Oct 30, 2024

What's your OS?

@kryptamine
Copy link
Author

mac os

@Saghen
Copy link
Owner

Saghen commented Oct 30, 2024

Does re-installing the plugin solve the issue for you? And if not, does adding build = "cargo build --release" fix the issue?

@kryptamine
Copy link
Author

I dont know what exactly did fix the issue, but adding build = "cargo build --release" and re-installing the plugin has helped

@Saghen
Copy link
Owner

Saghen commented Oct 30, 2024

Seems like a duplicate of #68

@Saghen Saghen closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2024
@kryptamine
Copy link
Author

Yep, thanks for help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants