Repository navigation
Add prompt to flip "inheritEnv" setting to false to fix conda activation issue #7607
Description
Activity
- addedfeature-requestRequest for new features or functionalityRequest for new features or functionalitytriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
on Sep 25, 2019 - ghost removedtriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
on Sep 25, 2019 - addedbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugand removedfeature-requestRequest for new features or functionalityRequest for new features or functionality
on Sep 25, 2019 karthiknadig commented
on Sep 25, 2019 MemberMore actionsIf the user dismisses (the "X") we should show it again. The context of the setting is User Setting, and should apply to all work spaces.
Just to make sure everyone understands what is the issue, the prompt is being displayed for Windows users (and apparently not for Mac nor Linux) as you can see here: #7861
Whoever works on this, please can you change the wording to specify that the changes will be on the settings.json file in the prompt, as described in the issue above? i.e. "[...], we suggest the "terminal.integrated.inheritEnv" setting to be changed to false in the settings.json file. [...]"setting to be changed to false in the settings.json file
Can I suggest we change as follows
setting to be changed to false in the settings (settings.json file)Novice users won't know what
settings.jsonfile is. VS Code has change the default settings configuration to a fancy UI and hidden thesettings.jsonfile behind the UI.I had to also run
conda init powershellin the VS code powershell terminal. After running that once, the correct env is activated in the future when creating powershell terminals in VS code. (Conda 4.7.12, VS Code 1.38.2, Python Ext 2019.10.41019)karthiknadig commented
on Oct 18, 2019 MemberMore actionsVerified on Windows with 2019.11.42782-dev: Nothing appeared when opening a workspace and selecting a conda environment.
Closing this issue and #7733.
- locked as resolved and limited conversation to collaborators
on Oct 26, 2019


To address #5764
if it isn't a Windows machine and if the selected interpreter is a conda environment and "terminal.integrated.inheritEnv" is not set on the user's user settings, we can prompt the message below:
"We noticed you're using a conda environment. If you are experiencing issues with this environment in the integrated terminal, we suggest the "terminal.integrated.inheritEnv" setting to be changed to false. Would you like to update this setting?"
Options: Yes, No
And add telemetry for the yes selection, so we can know if this is actually solving the issue.