-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pr #3088 made some commands not work.. #3093
Comments
The change you're referring to was in #2704, because |
i saw you check-in those all at |
While some |
not sure why you are saying it is not 'reliably', it had worked outside of gopath long time, |
Guru does not work reliably outside of GOPATH, because it relies on GOPATH and is not aware of modules at all. I am working to convert as many of the commands that relied on guru to use gopls as possible. |
um.. really? mostly my proj -or just a single tmp gofile it's not in gopath, even had no go-mod, but i recall i had used e.g |
While I've read many comments that guru doesn't work with modules and I know for sure that it uses I've created #3096 to re-enable the guru commands until I have a better understanding of the situations in which guru does not work with modules. |
some years passed, the situations maybe clear now, |
sorry, i mean gopls now mostly can replace them. |
in pr #3088 limits some command away -if 'go#package#InGOPATH()' was not true.
// e.g ':GoCallees' ':GoCallstack' etc not working..
but actually such commands were not so strict limited by gopath, it can be working in the past..
The text was updated successfully, but these errors were encountered: