Goto Definition: Difference between revisions
Jump to navigation
Jump to search
Adamcolton (talk | contribs) Created page with "I'd really like a better "goto definition" for Go, and it should be possible. https://github.com/DisposaBoy/GoSublime/issues/62 I need an idea of how the plug-in works. But ..." |
Adamcolton (talk | contribs) No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
I need an idea of how the plug-in works. But it should be possible to identify the type using the Go AST, identify where the package is imported from and jump to the right spot in the file. | I need an idea of how the plug-in works. But it should be possible to identify the type using the Go AST, identify where the package is imported from and jump to the right spot in the file. | ||
[https://github.com/DisposaBoy/GoSublime/tree/master/src/disposa.blue/cmd/margo_pkg This] seems to be the heart of the MarGo package. | |||
...on the other hand it looks like someone already did this and it was never merged. I may just want to look for a fork of gosublime that's actually maintained. | |||
[[Category:Code]] | [[Category:Code]] | ||
Latest revision as of 15:08, 16 May 2017
I'd really like a better "goto definition" for Go, and it should be possible.
https://github.com/DisposaBoy/GoSublime/issues/62
I need an idea of how the plug-in works. But it should be possible to identify the type using the Go AST, identify where the package is imported from and jump to the right spot in the file.
This seems to be the heart of the MarGo package.
...on the other hand it looks like someone already did this and it was never merged. I may just want to look for a fork of gosublime that's actually maintained.