# VSCode Julia Environment Installation Issue \`Find Definition\` Fails

**URL:** <https://discourse.julialang.org/t/vscode-julia-environment-installation-issue-find-definition-fails/82703>\
**Category:** New to Julia\
**Tags:** package\
**Created:** [June 13, 2022, 8:28pm UTC](https://discourse.julialang.org/t/vscode-julia-environment-installation-issue-find-definition-fails/82703 "2022-06-13T20:28:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![juliafriend](https://avatars.discourse-cdn.com/v4/letter/j/2acd7d/32.png) [@juliafriend](https://discourse.julialang.org/u/juliafriend)\
**Post date:** [June 13, 2022, 8:28pm UTC](https://discourse.julialang.org/t/vscode-julia-environment-installation-issue-find-definition-fails/82703/1 "2022-06-13T20:28:00Z")

</div>

I have a question about VSCode/Julia. I’ve already downloaded a repo from github and, in VSCode, I’ve selected the Julia environment to be the directory of the repo containing the Manifest.toml.

If I am developing within the `src` directory VSCode _can_ do `find definition` (F12).

However, if I want to use `find definition` in a file that’s importing `MyPackage`, we run into problems. Here’s what happens in the `tests/mytest.jl` file if I do a `find definition` for `MyPackage`

![Screen Shot 2022-06-13 at 4.15.47 PM](https://global.discourse-cdn.com/julialang/original/3X/1/4/144228bde1944af6f5718f6f1d6dcd3b8fe5fc97.png)

This confuses me because if MyPackage is installed in my Julia environment for VSCode, shouldn’t VSCode be able to run `find definition` anywhere the package is being used? The tutorial I’m following ([Developing Julia Packages - YouTube](https://www.youtube.com/watch?v=QVmU29rCjaA)) makes me this I shouldn’t be having this problem. However both in the tutorial and on Julia’s website ([5. Creating Packages · Pkg.jl](https://pkgdocs.julialang.org/v1/creating-packages/)), you start by using `generate` to create a blank package that gets installed in your current julia environment. I’m not generating a completely blank package (I’m starting from a fully developed package) so I assume this has something to do with my issue.

My background is Python.

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [June 13, 2022, 8:46pm UTC](https://discourse.julialang.org/t/vscode-julia-environment-installation-issue-find-definition-fails/82703/2 "2022-06-13T20:46:39Z")

</div>

Well, VSCode is far from perfect… I just accept that ‘goto definition’ sometimes works and sometimes it doesn’t.

Perhaps somebody else can explain better when it is expected to work and when it is not…

---

<div class="post-metadata">

**Author:** ![juliafriend](https://avatars.discourse-cdn.com/v4/letter/j/2acd7d/32.png) [@juliafriend](https://discourse.julialang.org/u/juliafriend)\
**Post date:** [June 14, 2022, 9:56pm UTC](https://discourse.julialang.org/t/vscode-julia-environment-installation-issue-find-definition-fails/82703/3 "2022-06-14T21:56:26Z")

</div>

Thanks 🙂

I’ve looked more into it and I think it had something to do with me developing a package outside of the `.julia/dev/` folder. I’ve got the tutorial working. We’ll see if I can get the other repo working.
