Repository navigation
Incorporate fixes from VSCode regarding Environment collection API #20822
Copy link
Copy link
Closed
Labels
area-terminalfeature-requestRequest for new features or functionalityRequest for new features or functionalityon-testplanAdded to test planAdded to test plan
Milestone
Description
Activity
- addedfeature-requestRequest for new features or functionalityRequest for new features or functionalityneeds proposalNeed to make some design decisionsNeed to make some design decisions
on Mar 9, 2023 karrtikr commented
on Mar 13, 2023 on Mar 13, 2023 · Hidden as resolvedAuthorshow commentMore actions- added a commit that references this issue
on Apr 11, 2023 - added a commit that references this issue
on May 26, 2023 - added a commit that references this issue
on Aug 10, 2023 - added a commit that references this issue
on Aug 23, 2023 - removedneeds proposalNeed to make some design decisionsNeed to make some design decisions
on Aug 28, 2023 - added 5 commits that reference this issue
on Sep 12, 2023 - locked as resolved and limited conversation to collaborators
on Sep 30, 2023
Metadata
Metadata
Labels
area-terminalfeature-requestRequest for new features or functionalityRequest for new features or functionalityon-testplanAdded to test planAdded to test plan
Results from spike #20492. Issues to tackle next to start using environment variables for activation:
envset in my fish config prevails over what I set in the env var collection vscode#184009Once these are done, implement using them in the Python extension:
pythonTerminalEnvVarActivationexperiment in multiroot workspaces #21101