Does nvim-cmp depend on the builtin completion or can it be disabled?

[mikehaertl]

The setup instructions of the README have this line for completeopt:

set completeopt=menu,menuone,noselect

From what I understand these settings relate to the builtin completion in vim. I wonder if this is really neccessary.

In my config I use <c-j> and <c-k> to navigate nvim-cmp completions. But I find myself often accidentally pressing <c-n> instead which seems to bring up the builtin vim completion in the background. So both (nvim-cmp + builtin completion) somehow conflict. I know that I could use the old default mappings - but that's not my point. I want to get used to <c-j> so <c-n> should have no mapping.

So I want to avoid this by completely disabling builtin completion via complete:

set complete=
set completeopt=

Is this a bad idea? Am I missing something where the builtin completion is still useful?

[Shougo]

You can disable built-in completion if not needed.
nvim-cmp does not depends on it.

[Shougo]

Because, plugins should not disable built in feature.
Other plugins may depend on it.

[mikehaertl]

I think you misunderstood. My question is why is this line required for nvim-cmp if it does not use the builtin completion:

nvim-cmp/README.md

Line 62 in 433af3d

set completeopt=menu,menuone,noselect

What is this for?

[Shougo]

Oh, I get it. It seems old. It is not needed anymore. Because it does not use native completion in default.

[mikehaertl]

I see, thanks. Maybe time to remove it then? 😉

[Shougo]

I think yes.