Error with built-in lsp completion about neovim

[AlejandroSuero]

I don't know if this is related to this issue, but it fits the title I guess, but this issue from supermaven-nvim seems to have a problem with built-in lsp completion.

• supermaven-inc/supermaven-nvim#59

From what I've been testing (videos in the issue) the main difference with nvim-cmp is:

• nvim-cmp when completing triggers:

# nvim-cmp
InsertCharPre
TextChangedI
InsertCharPre
TextChangedI
InsertCharPre
TextChangedI
InsertCharPre
InsertCharPre
InsertCharPre
InsertCharPre
InsertCharPre
InsertCharPre
InsertCharPre
TextChangedI

• built-in when completing triggers:

# vim.lsp.completion
InsertCharPre
TextChangedI
CompleteDone
CompleteChanged
TextChangedP
CompleteChanged
TextChangedP
CompleteChanged
TextChangedP
CompleteDone

Logs taken after video demo

built-in_vs_nvim-cmp.mp4

Logged out like:

  vim.api.nvim_create_autocmd({ "InsertChange", "InsertCharPre", "CompleteDone", "CompleteChanged", "TextChangedP", "TextChangedI", "TextChanged" }, {
    pattern = "*",
    group = M.augroup, -- ("supermaven", { clear = true }) for reference
    callback = function(event)
      if string.match(event.event, "Complete") then
        print(event.event)
      end
      if string.match(event.event, "Insert") then
        print(event.event)
      end
      if string.match(event.event, "TextChanged") then
        print(event.event)
      end
    end,
  })

And when writing with vim.lsp.completion triggered when using <C-x><C-o> it will behave the same but disables extmark for some reason, thus not getting the "ghost text" from the plugin. Same as you can see in the video if cycling through built-in completion.

Note

Tested both in v0.10.0 and nightly in MacOS 14.5 (23F79) in a tmux session in wezterm.