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

New tabs should re-read environment variable list. #19481

New Issue
Closed
opened 2026-01-31 06:44:41 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:44:41 +00:00
Owner
Copy Link

Originally created by @GarThor on GitHub (Mar 3, 2023).

Description of the new feature/enhancement

I'm not really sure if this should be filed as an issue or not, but I'm changing projects, and thusly environment variables all the time. Unfortunately, the terminal app runs as a single app, and never re-reads environment variables from the windows environment, which means I have to remember to close and re-open terminal if I want to see those changes. It would be nice if there was a button that would let me explicitly refresh the environment for a specific tab... at the very least closing and re-opening a tab should re-read the environment variables into the new shell for use.

Proposed technical implementation details (optional)

When I open a new terminal tab, it should have the most up-to-date version of all environment variables and other settings that I've set. This should be done in a predictable way, such that any process running in other tabs should retain the previous version of the environment variables, so that any processes running in those tabs doesn't get confused.

Originally created by @GarThor on GitHub (Mar 3, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> I'm not really sure if this should be filed as an issue or not, but I'm changing projects, and thusly environment variables all the time. Unfortunately, the terminal app runs as a single app, and never re-reads environment variables from the windows environment, which means I have to remember to close and re-open terminal if I want to see those changes. It would be nice if there was a button that would let me explicitly refresh the environment for a specific tab... at the very least closing and re-opening a tab should re-read the environment variables into the new shell for use. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> When I open a new terminal tab, it should have the most up-to-date version of all environment variables and other settings that I've set. This should be done in a predictable way, such that any process running in other tabs should retain the previous version of the environment variables, so that any processes running in those tabs doesn't get confused.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 06:44:41 +00:00
claunia commented 2026-01-31 06:44:43 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 3, 2023):

Thanks for the report! This is the topic of pull request #14839, which is associated with bug #1125. I've got good news: it looks like it's trending towards merging!

I'd suggest following /dup #1125 for a little longer, and jumping on the Preview channel when 1.18 is released. 😄

@DHowett commented on GitHub (Mar 3, 2023): Thanks for the report! This is the topic of pull request #14839, which is associated with bug #1125. I've got good news: it looks like it's trending towards merging! I'd suggest following /dup #1125 for a little longer, and jumping on the Preview channel when 1.18 is released. :smile:
claunia commented 2026-01-31 06:44:43 +00:00
Author
Owner
Copy Link

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

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Mar 3, 2023): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 06:44:43 +00:00
Author
Owner
Copy Link

@GarThor commented on GitHub (Mar 3, 2023):

Thanks so much @DHowett , I did search for the issue, and didn't immediately find anything that resembled this issue, but I suppose I just needed to dig a little deeper. I'll go ahead and take a look at the issues you posted, and then wait eagerly for the latest version! =D

@GarThor commented on GitHub (Mar 3, 2023): Thanks so much @DHowett , I did search for the issue, and didn't immediately find anything that resembled this issue, but I suppose I just needed to dig a little deeper. I'll go ahead and take a look at the issues you posted, and then wait eagerly for the latest version! =D
claunia commented 2026-01-31 06:44:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 3, 2023):

Oh, yeah, they're totally cryptic. We have a (bad?) habit of naming issues after the engineering work needed to do them rather than the observable bug. Sometimes. 😁

@DHowett commented on GitHub (Mar 3, 2023): Oh, yeah, they're totally cryptic. We have a (bad?) habit of naming issues after the engineering work needed to do them rather than the observable _bug_. Sometimes. 😁
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 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#19481
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?