Vscode is not following the executable path

I am having some trouble with Julia and VScode, so I decided to use (with juliaup) the lts version. I updated the path in VScode as I show in the image:

But even though, when I run a file or a line in VScode, it is still running version 1.11:


(Don’t know if it’s relevant, but I am using wsl)
What am I missing?

Did you execute juliaup default 1.10?

Thank you for your response. Yes, if I run julia in the terminal it runs the lts version.

Perhaps you should set this executable path: /home/msanchezr/.juliaup/bin/julia ?

I am going to try it. I was using the path I got from Sys.BINDIR, but that is a great point.

FWIW, VSCode caches the first path it has when loaded and keeps using that one. So if you were to update with Juliaup or change default channels while it is running, it won’t adjust. Restarting VSCode will allow it to find the new path. I believe I filed an issue for that.

I just updated Julia from version 1.9 to 1.10.5.
I changed the exec path parameter just by changing the version number and that seems to be enough.

Now, since the executable is in a seemingly different place, I wonder how vscode can find it.

julia> Sys.BINDIR
"C:\\Users\\sprmn\\.julia\\juliaup\\julia-1.10.5+0.x64.w64.mingw32\\bin"

Now I tried to point vscode to the new :grin: release of julia, but REPL (CTRL J+CTRL o) insists on using the old version

Okay, solved. I was editing on the user settings, but I needed to modify it in Remote (the wsl configuration)

2 Likes