In fact you can see all the folder it searches by running echo $PATH The default folders it searches are often /usr/local/bin, /usr/bin. It traverses through a variable called $PATH which contains a list of common directories that include binaries/executables. In Linux when you type in julia or any other command/executable, Linux needs to know where this executable exists on the file directory. And export is a linux command, nothing to do with VScode or Julia. A path in Linux is in the form /home/user/folder1/folder2/. When Julia is asking for a executable path … don’t put an export statement there. In summary, either you allow vscode to find Julia by going through the $PATH variable (which is what I would suggest) or you manually tell VScode where your Julia is by filling in the executable path variable in VSCode… I don’t think you need to do both.Īs I suspected. In this case, simply add the correct path to the executable path variable in VSCode. Ignore the export part (but you’ll lose the ability to simply type in julia anywhere in bash to launch).

Then if done properly, you don’t really need to fill in the executable path variable in VSCode. bashrc so that the Julia folder is in PATH as soon as you login to bash.

It seems like you put the verbatim command export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/brett/Julia/julia-1.5.3-linux-x86_64/julia-1.5.3/bin in the executable path variable of VScode, which is completely wrong.Īdd an export statement to your. bashrc or wherever you have the export command saved? Also could you post your VS Code settings (Click File → Settings) and show us your Julia executive path variable?

Visual studio code ubuntu