Does "completeFunctionCalls": false do what you want?

I have an existing expression f(a), and I would like to replace it with f(protocol.FWithLongName(a)). After typing protocol.F, the only useful completion offered is the function snippet, which would complete as
f(protocol.FWithLongName(x protocol.TypeWithLongName, y TypeOfSecondArg)(a))
which requires too much editing.

I agree that the completion logic needs to be smarter in this case.

Can you share your gopls setting? I disabled usePlaceholder for the similar issue at some point in the past.

@pjweinb i am not suggesting users have to turn on/off the settings while editing. I meant usePlaceholder setting became counter-productive due to this problem and I personally don't use that setting any more. Giving both option will be confusing unless we figure out good presentation, and make the suggestion list longer.

I wonder if we could try to make the snippet smarter. In f(a) where you want f(other(a, ...)), if a can be passed to other, maybe we could see that and offer other(a, <nextArg>) as the completion. Or maybe that is too specific.

Anyway, in cases where there is a trailing identifier after the cursor, I feel it is reasonable to also offer the naked function call as a completion candidate since it is hard to tell what the user wants.