"NO VERSION" with juliaup
#3189
-
|
I had installed Julia 1.8.0 with the regular installer. Then the Julia segment correctly showed that version in a Julia project folder. I upgraded to v1.8.3 by uninstalling the above version and installed Julia via juliaup from the Microsoft store. Julia itself is working fine, but now the Julia segment of Oh My Posh in the smae folder as above (just) shows
Is this a bug/missing feature in Oh My Posh or is this maybe caused by juliaup? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 29 replies
-
|
@Mo-Gul can you run oh-my-posh debug in that folder? |
Beta Was this translation helpful? Give feedback.
-
|
Sure, here the output, where I just replaced the real path to the project with `` and the real user name with output of "oh-my-posh debug" |
Beta Was this translation helpful? Give feedback.
-
|
@Mo-Gul ok, so it seems that here, |
Beta Was this translation helpful? Give feedback.
-
|
Searching my computer for
where the first two seem to be "real" executables (because they have the right symbol and have a size greater than 0) and the latter two are "not real" executables. And as it seems Maybe this helps ... |
Beta Was this translation helpful? Give feedback.
-
|
hmm, when I run
|
Beta Was this translation helpful? Give feedback.
-
|
@Mo-Gul I'll debug this again to see the result on my end. |
Beta Was this translation helpful? Give feedback.
-
|
@Mo-Gul this is something I can't fix as on my machine the rights are correct, same installation. 2022/12/11 09:41:56 CommandPath
C:\Program Files\WindowsApps\JuliaComputingInc.Julia_1.8.12.0_x64__b0ra4bp6jsp6c\Julia\julialauncher.exe
2022/12/11 09:41:56 CommandPath: 1.9994ms, args: julia
2022/12/11 09:41:56 HasCommand: 1.9994ms, args: julia
2022/12/11 09:41:56 RunCommand
julia version 1.8.3
2022/12/11 09:41:56 RunCommand: 79.327ms, args: julia --version |
Beta Was this translation helpful? Give feedback.
-
|
That is very unfortunate. I tested installing I'll ask the |
Beta Was this translation helpful? Give feedback.
-
|
@Mo-Gul this is on a VM, regular user. This functionality is only available due to a custom fork of golang btw, as Store Apps are something different and currently unsupported. I have a pull request ongoing at golang to add this and we changed the behavior a bit. Maybe I should update the fork as well. |
Beta Was this translation helpful? Give feedback.
-
|
I just stumbled over this, I'm the creator and maintainer of Juliaup. Juliaup uses an MSIX installer, and then uses MSIX execution aliases to make both One should not try to launch the binaries in I'm not entirely sure how oh-my-posh goes about detecting things, but the "official" sanctioned way for software to figure out whether Julia is installed via Juliaup and get information about installed versions is by launching |
Beta Was this translation helpful? Give feedback.
-
|
@Mo-Gul can you check on your end with the new intermediate build? Not sure if you can access the build artifacts. You'll need to replace your oh-my-posh version with the correct You can use the following to know the location of oh-my-posh.exe on your systen: (Get-Command oh-my-posh.exe).Source |
Beta Was this translation helpful? Give feedback.
-
|
@JanDeDobbeleer I just tried the intermediate build, and that fixes it for me :) And I can reproduce the problem with the current official build. |
Beta Was this translation helpful? Give feedback.
-
|
@JanDeDobbeleer, with v12.26.8 I finally see
again. Many thanks for fixing this issue. Also many thanks to @davidanthoff. You guys are awesome!! |
Beta Was this translation helpful? Give feedback.
-
|
@JanDeDobbeleer, I never used discussions before. Shall you or I write an(other) answer that I'll accept then or what is the way to go? |
Beta Was this translation helpful? Give feedback.
-
|
I guess this was an issue anyways so I'll convert back and close. |
Beta Was this translation helpful? Give feedback.
-
|
This was due to following the execution alias symlink which it shouldn't do according to information only found in GitHub issues. Cherry picking the latest version of the PR I have running for Golang does resolve the problem as we now return the same path and ignore the fact that it's an undocumented symlink. |
Beta Was this translation helpful? Give feedback.
This was due to following the execution alias symlink which it shouldn't do according to information only found in GitHub issues. Cherry picking the latest version of the PR I have running for Golang does resolve the problem as we now return the same path and ignore the fact that it's an undocumented symlink.