You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the release of v0.4.0, I was interested in this new config option, so I set it, restarted the shell; Windows Terminal running PowerShell Core (v7), and installed Python as this has the env_add_path variable and was referenced in the PR for the feature.
SCOOP_PATH is not created in the environment variables. What am I missing?
Expected Behavior
Create SCOOP_PATH and add %SCOOP_PATH% to PATH as referenced for the feature.
Additional context/output
Possible Solution
Not sure - I'm probably missing something, and appreciate any help to understand the feature better.
System details
Windows version: 11
OS architecture: 64 bit
PowerShell version: 7.4.2
Additional software: Not sure of anything relevant to the bug.
The text was updated successfully, but these errors were encountered:
RavenMacDaddy
changed the title
[Bug] use_isolate_path set to true
[Bug] use_isolate_path set to True doesn't create SCOOP_PATH in environment variables
Apr 18, 2024
Bug Report
Current Behavior
With the release of v0.4.0, I was interested in this new config option, so I set it, restarted the shell; Windows Terminal running PowerShell Core (v7), and installed Python as this has the
env_add_path
variable and was referenced in the PR for the feature.SCOOP_PATH is not created in the environment variables. What am I missing?
Expected Behavior
Create SCOOP_PATH and add %SCOOP_PATH% to PATH as referenced for the feature.
Additional context/output
Possible Solution
Not sure - I'm probably missing something, and appreciate any help to understand the feature better.
System details
Windows version: 11
OS architecture: 64 bit
PowerShell version: 7.4.2
Additional software: Not sure of anything relevant to the bug.
The text was updated successfully, but these errors were encountered: