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

Reload System Variable when opening a new TAB instead of reload the entire application #16937

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

Originally created by @Raffaello on GitHub (Mar 6, 2022).

Description of the new feature/enhancement

When installing something, for eg using winget, that changes the system path.
Windows terminal must be reloaded.
Instead would be more interesting, if it was enough to open a new tab for that.

Proposed technical implementation details (optional)

I guess when opening a new tab, is loading the user environmental settings and merge with the system settings.
The system settings are only loaded when windows terminal is opened the first time and "cached".

It might be interesting to have a way to reload them in a new tab.
It could be possible, i think, because at least once are read. So if those are changed should be possible to re-fresh them.

Ignoring for now the split screen.

if i am installing with winget github cli for instance.
that package add an environment system path to the gh.exe

that forces to close windows terminal and re open it again to apply that changes.
That is not a "big issue" but is just annoying.
Having something that could refresh the system variables and make them available to the next shell to open (just considering a new tab at the moment, but it could be in a split screen too), it would increase the productivity.

NOTE:
I am not sure neither honestly if it is related to the windows terminal or the shell in use or winget itself that should trigger something as a post install.
MY best guess is that is related to windows terminal as those system environmental variable looks like are loaded when loading the first time the app and then ignored after that, independently of the guest shell in use.

Originally created by @Raffaello on GitHub (Mar 6, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 When installing something, for eg using `winget`, that changes the system path. Windows terminal must be reloaded. Instead would be more interesting, if it was enough to open a new tab for that. <!-- 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). --> # Proposed technical implementation details (optional) I guess when opening a new tab, is loading the user environmental settings and merge with the system settings. The system settings are only loaded when windows terminal is opened the first time and "cached". It might be interesting to have a way to reload them in a new tab. It could be possible, i think, because at least once are read. So if those are changed should be possible to re-fresh them. Ignoring for now the split screen. <!-- A clear and concise description of what you want to happen. --> if i am installing with winget github cli for instance. that package add an environment system path to the `gh.exe` that forces to close windows terminal and re open it again to apply that changes. That is not a "big issue" but is just annoying. Having something that could refresh the system variables and make them available to the next shell to open (just considering a new tab at the moment, but it could be in a split screen too), it would increase the productivity. NOTE: I am not sure neither honestly if it is related to the windows terminal or the shell in use or winget itself that should trigger something as a post install. MY best guess is that is related to windows terminal as those system environmental variable looks like are loaded when loading the first time the app and then ignored after that, independently of the guest shell in use.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 05:27:47 +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 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#16937
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?