starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

New tabs inherit the environment of the Terminal process instead of the user default environment. #6389

New Issue
Open
opened 2026-01-31 00:37:25 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 00:37:25 +00:00
Owner
Copy Link

Originally created by @yitzhaks on GitHub (Feb 12, 2020).

Environment

Windows build number: 10.0.19559.0
Windows Terminal version (if applicable): 0.8.10261.0

Steps to reproduce

  1. In a terminal tab, run any command that modified the user/system environment (e.g. SETX).

Expected behavior

When opening a new tab, the environment should reflect the change made in step 1.

Actual behavior

The environment doesn't reflect the change made in step 1.
I assume this is because CreateProcessW is called with lpEnvironment == nullptr which means the new process uses the environment of the calling process.

This is frustrating since if one makes a change to the user/system environment, one needs to close all Terminal tabs (or start a new Terminal) to get a tab that reflects said change.

Originally created by @yitzhaks on GitHub (Feb 12, 2020). # Environment ```none Windows build number: 10.0.19559.0 Windows Terminal version (if applicable): 0.8.10261.0 ``` # Steps to reproduce 1. In a terminal tab, run any command that modified the user/system environment (e.g. SETX). # Expected behavior When opening a new tab, the environment should reflect the change made in step 1. # Actual behavior The environment doesn't reflect the change made in step 1. I assume this is because `CreateProcessW` is called with `lpEnvironment == nullptr` which means `the new process uses the environment of the calling process`. This is frustrating since if one makes a change to the user/system environment, one needs to close all Terminal tabs (or start a new Terminal) to get a tab that reflects said change.
claunia added the Resolution-Duplicate label 2026-01-31 00:37:25 +00:00
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 Resolution-Duplicate
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#6389
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?