I know there have been several threads on this topic already. Examples include going to definitions in packages or included definitions. Most of these threads just seem to be dangling with no resolution. In my experience, “go to definition” almost never works. [Screenshot 2023-03-01 at 11.03.24] P…

When I have a package open for development, VSC does not recognize its methods, and jumping to definition does not work. I already asked about this, and I don’t think I got a definitive answer.

It does for me but I think one must have the entire directory (normally the src dir) loaded in the EXPLORER such that it can sniff in all files that may have the type/function definition.

What happens if you open a new file and try the example above?

This seems to be coming up more often (i.e. Go To Definition (F12) does not work for functions in an included file ). I had a workflow that used to work okay (required a few Julia language server restarts every so often) but recently it doesn’t work and I can’t access intellisense (and hence go to de…

Not immediately, and if fact I’m not exactly sure what made it work but I think it was the fact that I include("testa.jl") in the module and in the VSC repl I did a using *package* [image]

I’ll give those things a try (I already do the first one). But it seems, that is at best temperamental and unreliable.

Interestingly, in my case if the change the type from an abstract type to a struct, it suddenly works. I think I will raise an issue.

I think the main, underlying issue is the lack of documentation of the StaticLint, see: Request for a more specific example or documentation on StaticLint · Issue #310 · julia-vscode/StaticLint.jl · GitHub If StaticLint would be better documented and could be used and tested stand-alone more people…

Another very simple example - unable to find the module in the module project. It’s also unable to find the definition of greet. [image]

Go to definition almost never works

Tooling

Christopher_Fisher March 1, 2023, 11:45pm 9

Unfortunately, this has been a longstanding issue for me. I reported this issue in 2021.

VSCode vs Intellij Julia support

Topic		Replies	Views
Go to definition in VSCode not working for packages VS Code question	2	3232	August 3, 2021
VSCode's 'Go to definition' to recognise functions from other libraries VS Code question	6	2161	November 2, 2023
VSCode Julia Environment Installation Issue `Find Definition` Fails New to Julia package	2	291	June 14, 2022
Broken links in VSCode DocStrings e.g. 'PLACEHOLDER/core.js' New to Julia	3	356	April 4, 2022
"Go to defintition (F12)" doesn't work for functions in a package VS Code	4	737	February 21, 2023

Go to definition almost never works

Related topics