Is blink.cmp adding parenthesis when completing from the LSP source?

[cuducos]

I am trying to understand why when I migrated from nvim-cmp to blink.cmp, every time I import a function using blink.cmp's LSP source, parenthesis are automatically added. This is terrible.

1. First because it is personal, people should be able to config if they want parenthesis added or not (I, personally, hate it)
2. Because in many scenarios it is just wrong — for example, using Python on import or when treating functions as first-class citizens (passing them as function arguments instead of calling them)

For example:

from urlllib.parse import urlj
#             cursor position ^ 

Then the blink.cmp menu shows up beautifully, and I select urljoin from the LSP source. Hit C-y (default mapping) and get:

from urllib.parse import urljoin()
#                cursor position ^ 

This is just wrong Python code. And I am trying to map what is causing that, and if it's blink.cmp if there is a way to disable these parenthesis as part of the auto-completion.

[Saghen]

Please read the docs: https://cmp.saghen.dev/configuration/completion.html#auto-brackets and https://cmp.saghen.dev/configuration/reference.html#completion-accept

[Saghen]

I've also opened an issue for supporting special cases: #1008

[cuducos]

Thank you, @Saghen! I looked for parenthesis and then missed that entry. You saved the day 💜

[cuducos]

Ah, if anyone else gets here looking for the solution, the links above helped me turn this feature off. TLDR, added that to my opts:

completion = { accept = { auto_brackets = { enabled = false } } },