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
I'm hoping there's a way to specify a broader scope for the search, so that all references to a symbol in a larger project can be identified, not just the ones which happen to be in the same package as the file I'm currently visiting.
What did you see instead?
Here is the message lsp-mode is sending to gopls, on an lsp-find-references request:
lsp-mode only seems to be getting back references to the symbol at file.go:23:45 in the same package as file.go's. Is there a way to expand the search scope?
Probably less relevant questions from the template:
What version of Go are you using (go version)?
$ go version
go version go1.12.1 linux/amd64
Does this issue reproduce with the latest release?
It does with go get golang.org/x/tools/gopls@latest, at least.
What operating system and processor architecture are you using (go env)?
What did you do?
I'd like to use the emacs
lsp-mode
client to find references to a symbol, but itslsp-find-references
only returns references to the symbol in the current golang package.What did you expect to see?
I'm hoping there's a way to specify a broader scope for the search, so that all references to a symbol in a larger project can be identified, not just the ones which happen to be in the same package as the file I'm currently visiting.
What did you see instead?
Here is the message
lsp-mode
is sending togopls
, on anlsp-find-references
request:lsp-mode
only seems to be getting back references to the symbol atfile.go:23:45
in the same package asfile.go
's. Is there a way to expand the search scope?Probably less relevant questions from the template:
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
It does with
go get golang.org/x/tools/gopls@latest
, at least.What operating system and processor architecture are you using (
go env
)?go env
OutputThe text was updated successfully, but these errors were encountered: