# VScode with custom DEPOT\_PATH

**URL:** <https://discourse.julialang.org/t/vscode-with-custom-depot-path/101909>\
**Category:** New to Julia\
**Tags:** vscode\
**Created:** [July 21, 2023, 8:46pm UTC](https://discourse.julialang.org/t/vscode-with-custom-depot-path/101909 "2023-07-21T20:46:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![discourserogu](https://avatars.discourse-cdn.com/v4/letter/d/919ad9/32.png) [@discourserogu](https://discourse.julialang.org/u/discourserogu)\
**Post date:** [July 21, 2023, 8:46pm UTC](https://discourse.julialang.org/t/vscode-with-custom-depot-path/101909/1 "2023-07-21T20:46:08Z")

</div>

I’m trying to get Julia to work in VScode with a custom DEPOT\_PATH, I know for general execution you could use

```julia
JULIA_DEPOT_PATH=\path\to\dir julia

```

and it would work. How do I accomplish the same for working with VScode?

---

<div class="post-metadata">

**Author:** ![Salmon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/salmon/32/22968_2.png) [@Salmon](https://discourse.julialang.org/u/Salmon)\
**Post date:** [August 21, 2023, 3:28pm UTC](https://discourse.julialang.org/t/vscode-with-custom-depot-path/101909/2 "2023-08-21T15:28:58Z")

</div>

bumping this since I have the same issue.

for some reason, vscode prefers to create a new folder in ~/.julia instead of using the existing one at DEPOT\_PATH.

Does anyone know how to circumvent this? I know that it _can_ work in principle since I do not have this issue on a different machine, but I do not understand the problem.

It looks like vscode does not use ~/.bashrc …

---

<div class="post-metadata">

**Author:** ![Salmon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/salmon/32/22968_2.png) [@Salmon](https://discourse.julialang.org/u/Salmon)\
**Post date:** [September 13, 2023, 6:07am UTC](https://discourse.julialang.org/t/vscode-with-custom-depot-path/101909/3 "2023-09-13T06:07:59Z")

</div>

It’s been a while but in case anyone wonders, in my case the problem is solved by starting up vscode from the shell (so that it knows the environment variables)