starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Set environment variable in current shell from child process #23014

New Issue
Closed
opened 2026-01-31 08:29:56 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:29:56 +00:00
Owner
Copy Link

Originally created by @peakschris on GitHub (Mar 11, 2025).

Description of the new feature

We launch a python CLI from windows terminal. As a result of certain CLI actions, we want the windows terminal to set certain environment variables as soon as the python CLI command finishes. I understand that this is impossible when launching python from CMD. However, maybe there is some trick to allow it when launching python from Windows Terminal.

We have discarded the option of wrapping the python CLI in a bat or cmd as then we end up with the dreaded 'Terminate (Y/N)' prompt on Ctrl-C.

My hope is that Windows Terminal has some kind of scripting support such that the python subprocess can add an envvar in its parent shell via some kind of API call.

Any other ideas very welcome!

Proposed technical implementation details

No response

Originally created by @peakschris on GitHub (Mar 11, 2025). ### Description of the new feature We launch a python CLI from windows terminal. As a result of certain CLI actions, we want the windows terminal to set certain environment variables as soon as the python CLI command finishes. I understand that this is impossible when launching python from CMD. However, maybe there is some trick to allow it when launching python from Windows Terminal. We have discarded the option of wrapping the python CLI in a bat or cmd as then we end up with the dreaded 'Terminate (Y/N)' prompt on Ctrl-C. My hope is that Windows Terminal has some kind of scripting support such that the python subprocess can add an envvar in its parent shell via some kind of API call. Any other ideas very welcome! ### Proposed technical implementation details _No response_
claunia commented 2026-01-31 08:29:58 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Mar 12, 2025):

Thank you for the request! Unfortunately Terminal does not have any special control over the environments of running processes.

Just curious - why do you want the environment variables in CMD while running Python /?

@PankajBhojwani commented on GitHub (Mar 12, 2025): Thank you for the request! Unfortunately Terminal does not have any special control over the environments of running processes. Just curious - why do you want the environment variables in CMD while running Python /?
claunia commented 2026-01-31 08:29:58 +00:00
Author
Owner
Copy Link

@peakschris commented on GitHub (Mar 12, 2025):

So to be clear, I don't want terminal to change the environment of a running process. I want the running process to change the terminal's environment so that it will apply to any future commands that are invoked.

@peakschris commented on GitHub (Mar 12, 2025): So to be clear, I don't want terminal to change the environment of a running process. I want the running process to change the terminal's environment so that it will apply to any future commands that are invoked.
claunia commented 2026-01-31 08:29:58 +00:00
Author
Owner
Copy Link

@peakschris commented on GitHub (Mar 12, 2025):

Why? We have a python CLI that has multiple options. One of those is 'install devtools'. This creates a new bin directory in a new location. We want these tools to be available immediately after this CLI invocation is finished, without the developer needing to restart terminal. So we'd like the python CLI to be able to update the PATH envvar that the terminal will use for future commands.

@peakschris commented on GitHub (Mar 12, 2025): Why? We have a python CLI that has multiple options. One of those is 'install devtools'. This creates a new bin directory in a new location. We want these tools to be available immediately after this CLI invocation is finished, without the developer needing to restart terminal. So we'd like the python CLI to be able to update the PATH envvar that the terminal will use for future commands.
claunia commented 2026-01-31 08:29:59 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 12, 2025):

Ah, sorry about that.

Terminal automatically reloads the environment from the registry for every new pane and every new tab! That is, unless the user has disabled that feature by setting compatibility.reloadEnvironmentVariables to false (or toggled this setting in the Advanced settings page:

Image

)

Even so, when I read...

the terminal will use for future commands

... I still can't help but think you want the currently running shell (pwsh.exe, cmd.exe, powershell.exe) to reload.

At the end of the day, it is still the shell which is running your commands. Any process that is already running when you update the environment--including the shell--is immune to those changes.

That's what we mean when we say "running process". 🙂

To put it differently:

I understand that this is impossible when launching python from CMD. However, maybe there is some trick to allow it when launching python from Windows Terminal.

There is no dichotomy here: CMD is still running, it's just inside Terminal.

@DHowett commented on GitHub (Mar 12, 2025): Ah, sorry about that. Terminal automatically reloads the environment from the registry for every new pane and every new tab! That is, unless the user has disabled that feature by setting `compatibility.reloadEnvironmentVariables` to `false` (or toggled this setting in the Advanced settings page: ![Image](https://github.com/user-attachments/assets/83510508-a1a6-4b02-ac51-c1bc8035245d) ) Even so, when I read... > the terminal will use for future commands ... I still can't help but think you want the currently running shell (pwsh.exe, cmd.exe, powershell.exe) to reload. At the end of the day, it is still the shell which is running your commands. Any process that is *already running* when you update the environment--including the shell--is immune to those changes. That's what we mean when we say "running process". 🙂 --- To put it differently: > I understand that this is impossible when launching python from CMD. However, maybe there is some trick to allow it when launching python from Windows Terminal. There is no dichotomy here: CMD is still running, it's just inside Terminal.
claunia commented 2026-01-31 08:29:59 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Mar 24, 2025):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Mar 24, 2025): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23014
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?