[Bug]: reshim isn't creating shims

[BradKnowles]

Description

I run dtvem reshim and it says it worked, but when I go to $Env:USERPROFILE\.dtvem\shims it is an empty directory.

Steps to Reproduce

1. Run dtvem reshim
2. Profit? 😄

Expected Behavior

I expect shims to be present so I can access python / node in the CLI.

Actual Behavior

No shims are created

Operating System

Windows

dtvem Version

0.5.5

Go Version (if building from source)

No response

Which runtime is affected?

Not runtime-specific

Error Messages / Logs

No error messages are displayed

Configuration

Additional Context

I will say I'm running this in a corporate VDI. I do have admin rights, so it shouldn't be a permissions thing, but worth mentioning.
The runtimes are installed, I can invoke them from the full $Env:USERPROFILE\.local\share\dtvem\version\python\... path, but the shims aren't being created.

Code of Conduct

• I agree to follow this project's Code of Conduct

[CalvinAllen]

@BradKnowles Which method did you use to get dtvem under $Env:USERPROFILE\.local\share\? XDG_DATA_HOME?

Is there by chance, any shims at $Env:USERPROFILE\.local\share\dtvem\shims?

[BradKnowles]

Yes, I have XDG_DATA_HOME set, as well as several others variables.

Variable	Value
XDG_BIN_HOME	C:\Users\Brad.Knowles\.local\bin
XDG_CACHE_HOME	C:\Users\Brad.Knowles\.cache
XDG_CONFIG_HOME	C:\Users\Brad.Knowles\.config
XDG_DATA_HOME	C:\Users\Brad.Knowles.\local\share
XDG_STATE_HOME	C:\Users\Brad.Knowles\.local\state

There are shims at that location, but it is not in my PATH.

My path is this..

C:\Program Files\PowerShell\7
C:\Users\Brad.Knowles\.dtvem\shims
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Windows\System32\OpenSSH\
C:\Program Files\PowerShell\7\
C:\Program Files\Microsoft SQL Server\170\Tools\Binn\
C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\
C:\Program Files\dotnet\
C:\Users\Brad.Knowles\scoop\apps\vscode\current\bin
C:\Users\Brad.Knowles\scoop\apps\gpg-np\current\bin
C:\Users\Brad.Knowles\scoop\apps\git\current\cmd
C:\Users\Brad.Knowles\.local\share\dtvem\bin
C:\Users\Brad.Knowles\scoop\shims
C:\Users\Brad.Knowles\AppData\Local\Microsoft\WindowsApps
C:\Users\Brad.Knowles\.dotnet\tools

[CalvinAllen]

Ah, gotcha, so it used the default shims location in the PATH and not the custom one - working through it now!

[CalvinAllen]

@BradKnowles Alright, got it - when the next release hits and after you update, run dtvem init again and it will "resolve" the PATH mismatch for the shims folder.