After I installed 1.8 I deleted my GOPATH environment variable, but VSCode didn't like that, so I created GOPATH variable again, this time pointing to
%USERPROFILE%\go While I were at it, I extended my PATH variable to include the bin from GOPATH %USERPROFILE%\go\bin Don't forget to drop dlv.exe somewhere in your PATH, so that VSCode can find it. Mine is in %USERPROFILE%\go\bin . On Wednesday, March 1, 2017 at 9:44:52 PM UTC-3, ziffusion wrote: > > I tried delve with VSCode, and had a problem with GOPATH. For some reason > the debugger saw a GOPATH that was different from the one set in the > environment or VSCode settings. > > Anyone have any input on this? > > On Wednesday, March 1, 2017 at 6:18:43 PM UTC-5, JuciÊ Andrade wrote: >> >> Nyah, there are several IDEs capable of controlling Delve under the hood >> to debug Go programs. It works nicely. >> If you are used to Visual Studio you will feel in home with VSCode. Even >> shortcuts for debugging are the same. >> >> On Wednesday, March 1, 2017 at 4:32:09 PM UTC-3, Nyah Check wrote: >>> >>> >>> >>>> Great! Hope it continues to work for you. We're constantly working to >>>> improve the debugging experience for Go, so feel free to reach out via our >>>> mailing list or Github if you run into any issues or have any ideas for >>>> improvement. >>>> >>>> >>> Will do >>> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
