when cmdline candidate selected, the window will jump up to the top of the window

[winkee01]

This is completion menu when I type something:

When I move the selection to LspInfo, the menu will jump to the top of the window, very unpleasant !

Can someone please tell me what is the reason for that? how can I fix it?

[soifou]

It's hard to pinpoint the issue with just two screenshots. I recommend trying to isolate the problem by disabling other plugins that might be interfering and/or commenting out parts of your blink configuration.

If possible, it would be even better if you could reproduce this behavior using a minimal example file, such as main/repro.lua. That way, we can take a closer look

[winkee01]

Hi, thank you for the reply, if you enable the cmdline source, it is very easy to repreduce the issue. I have actually tested with your provided main/repro.lua, and it reproduced the issue. here is the config:

vim.env.LAZY_STDPATH = '.repro'
load(vim.fn.system('curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua'))()

require('lazy.minit').setup({
  spec = {
    {
      'saghen/blink.cmp',
      build = 'cargo build --release',
      opts = {
        completion = {
          keyword = { range = 'full' },
          accept = { auto_brackets = { enabled = false }, },
          list = { selection = { preselect = false, auto_insert = true } },
          menu = {
            auto_show = true,
            draw = {
              padding = 2,
              columns = {
                { "label", "label_description", gap = 1 },
                { "kind_icon", "kind" },
                { 'source_name' },
              },
              components = {
                source_name = {
                  width = { max = 30 },
                  text = function(ctx) return '[ ' .. ctx.source_name ..' ]' end,
                  highlight = 'BlinkCmpSource',
                }
              }
            }
          },
          documentation = { auto_show = true, auto_show_delay_ms = 500 },
          ghost_text = { enabled = true },
        },

        sources = {
          default = { 'lsp', 'path', 'snippets', 'buffer', 'cmdline' },
        },

        fuzzy = { implementation = 'prefer_rust_with_warning' },
        snippets = { preset = 'default' }, 
        signature = { enabled = true },
      },
    },
    {
      'neovim/nvim-lspconfig',
      dependencies = {'mason.nvim', },
      opts = {
        servers = {
          lua_ls = {},
        },
      },
      config = function(_, opts)
        require("mason").setup()
        local lspconfig = require('lspconfig')
        for server, config in pairs(opts.servers) do
          config.capabilities = require('blink.cmp').get_lsp_capabilities()
          lspconfig[server].setup(config)
        end
      end,
    },
  },
})

[soifou]

Thanks for providing a reproducer!

You added inadvertently cmdline in sources.default. You don't need to declare this "source" since it's builtin :)
Remove it and you'll be fine:

sources = {
   default = { 'lsp', 'path', 'snippets', 'buffer' },
},

If you need to configure the cmdline behavior (keymaps, menu appareance and such), please read https://cmp.saghen.dev/modes/cmdline.html

[soifou]

Hence the link to the doc :D

Particulary this paragraph https://cmp.saghen.dev/modes/cmdline#show-menu-automatically

[winkee01]

I think you get me wrong. the situation is, I am typing in INSERT mode, not in cmdline mode. and I enabled the cmdline source when I am typing in INSERT mode. and that's the problem, when in INSERT mode, the cmdline source is causing the disfunctioning of the completion menu.

[soifou]

It surely is too late for me but I ask anyway ; why do you need cmdline source in insert mode? Why do you want LspInfo suggested in a lua file?

cmdline is supposed to be used (as the name suggest) in command mode only. LspInfo is a command. default = {} are source providers for insert mode, not terminal nor cmdline. And this is why you see this (unexpected) behavior.

[winkee01]

[winkee01]

Yes, sometimes I think i may need cmdline source in Insert mode, not quite a frequent use, but anyway, if you expect people to not use cmdline source in INSERT mode why not ban it instead of misfunctioning or causing random bugs? I don't think it is semantically wrong to use cmdline source or any other sources in insert mode, even if it is not a regular case.

[soifou]

if you expect people to not use cmdline source in INSERT mode why not ban it instead of misfunctioning or causing random bugs?

Fair point, might need to add an additional check for this!