You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > Go: Locate Configured Go Tools
There is no such thing
based on the statement above, I think the Go extension is disabled or not installed. Because the command Go: Locate Configured Go Tools only exist if the go extension is installed and actively running. If you have it installed, you should be able to trigger this command like below.
Could you confirm if the Go extension is installed in your vscode? The Go extension in screenshot below. If you have it installed, try reload the window and see if the auto completion is working again.
Thank you.
If you still experience the issue, could you make a screenshot and share the output of Go: Locate Configured Go Tools?
h9jiang
added
the
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
label
Mar 19, 2025
I uninstalled the plugin and re-installed it again. Now there is the tools line - saved the output to: tools.md.
Anyway, code completion still does not work at all and also noticed a misbehaving context menu: on a right mouse click the context menu should open and stay open 'til it receives a left mouse click or an Esc event. But it doesn't - it immediately selects the menu item which is at the mouse pointer's position - really annoying misbehavior and not easy to find out, what the unintended instruction actually did to the code/editor ...
What version of Go, VS Code & VS Code Go extension are you using?
Go: Locate Configured Go Tools
There is no such thing
Share the Go related settings you have added/edited
Describe the bug
There is no code completion at all. It just behaves like a normal text editor.
Steps to reproduce the behavior:
load a go file an try to edit.
Actually it is a real pain to work with it. Even vim does a better job ...
The text was updated successfully, but these errors were encountered: