The new version of vscode Julia extension does not pick up the julia.exe in the path, but rather insists on using juliaup to install (some version of) it. Not very nice. I mean, I have the whole thing set up with a place for the depot etc. and that goes out the window. I am not sure where to inquire…

Although I understand your frustration, I don’t understand why some people are against juliaup. I have read some thread about this and the supposed difficulty of installing julia on Windows. To me, downloading the Julia installer, creating an environment variable to access julia everywhere or downl…

This should only be happening if the julia.executablePath setting is completely empty. In that case we nudge you towards either using juliaup or explicitly referencing a binary there (including a simple julia or julia.exe). If this is happening when the setting is not empty, then please open an is…

[image] Maucejo: Although I understand your frustration, I don’t understand why some people are against juliaup. I have read some thread about this and the supposed difficulty of installing julia on Windows. Actually I’d argue it is the easiest on Window. Unzip the Zip file to whenever you …

[image] Maucejo: Although I understand your frustration, I don’t understand why some people are against juliaup. Other than the reasons mentioned by Roy, I’ll add, I want to stay with Julia 1.10 and I don’t want to fight with the system to be able to do that.

[image] joa-quim: I want to stay with Julia 1.10 and I don’t want to fight with the system to be able to do that. You mean this fight? juliaup add 1.10 juliaup default 1.10

Putting julia/julia.exe into the julia.executablePath setting should fully recover the previous behaviour. If it doesn’t, open an issue. I get that changes in default behaviour are annoying, but this is fixable with a click and five keystrokes starting from the modal popup. That said, …

Thanks for considering an easier way of keeping the old behaviour! [image] The option to configure the path is indeed here. But the default is juliaup. (Since, in my case, julia.exe IS on the PATH at this point, the dialog is really unnecessary, it would seem?) Don’t get me wrong, I think juli…

Btw: some logic must have changed. I don’t see the button in the status bar that used to indicate that the LS was aware of the current environment. In fact the LS hover help that used to work does not work anymore (e.g. LinearAlgebra functions are not recognized). [image] I did [image] but [im…

Yes, that and my strange stubbornness that in my computer I like to decide where software is installed. And I hate software installed under hidden directories.

Forced to use juliaup: not cool

Tooling VS Code

Topic		Replies	Views
[ANN] Juliaup Preview - Julia version manager and Windows Store installer Community announcement , juliaup	94	12485	March 13, 2022
Error occured after the first precompilation on some packages after upadting to Julia 1.8.4 Package Management plots , juliaup	4	809	December 26, 2022
Best way to Re-Install Julia on new computer? New to Julia installation	32	2730	January 22, 2024
How to change Julia version in VSCode? VS Code vscode , versions , path	24	15176	September 30, 2022
Julia in vscode keeps precompiling compiled packages General Usage precompilation , vscode	11	799	August 21, 2024

Forced to use juliaup: not cool

Related topics