# Go to definition almost never works

**URL:** <https://discourse.julialang.org/t/go-to-definition-almost-never-works/95363>\
**Category:** Tooling\
**Tags:** vscode\
**Created:** [March 1, 2023, 12:26am UTC](https://discourse.julialang.org/t/go-to-definition-almost-never-works/95363 "2023-03-01T00:26:01Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jmair](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmair/32/35117_2.png) [@jmair](https://discourse.julialang.org/u/jmair)\
**Post date:** [March 1, 2023, 8:31am UTC](https://discourse.julialang.org/t/go-to-definition-almost-never-works/95363/5 "2023-03-01T08:31:41Z")

</div>

This seems to be coming up more often (i.e. [Go To Definition (F12) does not work for functions in an included file](https://discourse.julialang.org/t/go-to-definition-f12-does-not-work-for-functions-in-an-included-file/76293)). 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 definition) in most of my own files.

General advice that may or may not help:

- Open the project as a folder in VS code, instead of individual files.
- Create an environment for your project and activate that in VS code
- If you are using modules, adopt a standard package structure - e.g. using `PkgTemplates.jl`.

---

_[View the full topic](https://discourse.julialang.org/t/go-to-definition-almost-never-works/95363)._