blink.cmp and mini.completion #1472
-
Contributing guidelines
Module(s)mini.completion QuestionMy issue is documented here Saghen/blink.cmp#949 From mini.completion docs, I think it uses some sort of (neovim default?) fallback completion. Would it be possible to add mini.completion as some sort of source for blink.cmp? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Enabling both 'mini.completion' and 'blink.cmp' is a bad idea: they both provide autocompletion functionalities which will conflict with one another. What you're seeing as "words from another buffer/file" are indeed words from all loaded buffers (probably, only listed buffers, to be precise) and come from built-in Neovim (and Vim) completion. See The best way for 'blink.cmp' to support this kind of completion is through its own implementation as a different source. |
Beta Was this translation helpful? Give feedback.
Enabling both 'mini.completion' and 'blink.cmp' is a bad idea: they both provide autocompletion functionalities which will conflict with one another.
What you're seeing as "words from another buffer/file" are indeed words from all loaded buffers (probably, only listed buffers, to be precise) and come from built-in Neovim (and Vim) completion. See
:h i_CTRL-N
. It is a highly built-in feature which doesn't have a good way of utilizing it other than actually simulating pressing<C-n>
. It is also blocking/synchronous which has noticeable lagging when there is a very large buffer opened (like 10K - 100K lines depending on the machine).The best way for 'blink.cmp' to support this kind of compl…