gopls: set editor.suggest.snippetsPreventQuickSuggestions to true by default #839
Comments
I think this is a VSCode issue. Try adding the below to your settings:
@stamblerre should the Go extension set this by default? I don't really know the full impact. |
yes, you are right. Setting this option resolved the issue. Shall we keep it open until we figure out if we extension should set it to |
|
Thank you for the suggestions. I solved my problem by changing the |
@hyangah: What do you think about switching the default here? Or should we just stay in line with VS Code defaults? |
FYI I have been using this setting ever since you recommended it to me and I have seen no issues with it. |
@stamblerre I've been using the setting for a while and have no objection to switch the default. |
Change https://golang.org/cl/310754 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Haven't tried, but pretty sure it will. Can try it, if necessary.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What the problem is is better explained with video:
I am typing the function
acceptString
, I get a completion hint, clickEnter
and am send to enter the function arguments. However, once there the autocompletion does not work - it does not suggest anything to me, even when I start writing the function name(or variable name).Workaround: If I press

Esc
twice, the autocompletion is working again. See:Here, I type
ret
, then pressEsc
twice, and upon pressingu
I get a suggestion to usereturnString
. However, now I have lost the parameter hints and have to trigger them again, which is not ideal for functions that accept more than 1 argument.What did you expect to see?
I expect to have suggestions upon clicking
Enter
and start entering something.What did you see instead?
No suggestions, until I press
Esc
twice and get out of that context.I am willing to work on this and contribute a PR, if you would help me with finding where approximately is the code that handles this.
The text was updated successfully, but these errors were encountered: