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

Add Reload/Restart Action - i.e. vscode's Reload Window #21684

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

Originally created by @g0t4 on GitHub (May 10, 2024).

Description of the new feature/enhancement

Often I find myself wanting to restart Windows Terminal, it would be nice to have a stock command/action in the Command Palette. Something similar to vscode's Developer: Reload Window

Proposed technical implementation details (optional)

Two use cases come to mind:

  • I modify settings and want to reload to ensure changes are loaded... this could be fixed via changing how settings apply to auto-reload like it used to but I assume that's not the direction settings are headed, in which case this feature becomes invaluable.
  • I modify env vars and want to ensure they are picked up. I understand there is a new setting to open new tabs/panes with the new env block and that is great, but sometimes I want to ensure all my tabs/panes have the new block in which case just killing all of them and restarting would be great.

I do not personally need to re-open tabs/panes that were closed, instead I can start with a single new tab. That said, the new option to restore pane contents when starting terminal would likely work well with a restart action.

The net effect would be to terminate (close all windows/tabs/panes) the wt.exe process and then relaunch it. Or, if there is a way to do that without killing / starting a new process that would be fine too.

Originally created by @g0t4 on GitHub (May 10, 2024). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Often I find myself wanting to restart Windows Terminal, it would be nice to have a stock command/action in the `Command Palette`. Something similar to vscode's `Developer: Reload Window` # Proposed technical implementation details (optional) Two use cases come to mind: - I modify settings and want to reload to ensure changes are loaded... this could be fixed via changing how settings apply to auto-reload like it used to but I assume that's not the direction settings are headed, in which case this feature becomes invaluable. - I modify env vars and want to ensure they are picked up. I understand there is a new setting to open new tabs/panes with the new env block and that is great, but sometimes I want to ensure all my tabs/panes have the new block in which case just killing all of them and restarting would be great. I do not personally need to re-open tabs/panes that were closed, instead I can start with a single new tab. That said, the new option to restore pane contents when starting terminal would likely work well with a restart action. The net effect would be to terminate (close all windows/tabs/panes) the wt.exe process and then relaunch it. Or, if there is a way to do that without killing / starting a new process that would be fine too.
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 07:51:56 +00:00
claunia commented 2026-01-31 07:51:57 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 10, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (May 10, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Closed similar issues: - [Add command palette item to restart the window (#13416)](https://github.com/microsoft/terminal/issues/13416), similarity score: 0.84 - [Reload (restart) the current tab (#15872)](https://github.com/microsoft/terminal/issues/15872), similarity score: 0.78 - [Implement a keybinding to restart/reload a tab (#3726)](https://github.com/microsoft/terminal/issues/3726), similarity score: 0.75 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:51:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 10, 2024):

I modify settings and want to reload to ensure changes are loaded... this could be fixed via changing how settings apply to auto-reload like it used to

It still does! I suspect though what you're seeing is that when you save a fragment file, the Terminal doesn't hot-reload that. I could have swore there was an issue for that. You can just touch the main terminal settings file to have it hot-reload the fragments too.

The terminal will continue to always support hot-reloading its own settings file. I'm not about to break that any time soon 😄

I modify env vars and want to ensure they are picked up. I understand there is a new setting to open new tabs/panes with the new env block and that is great, but sometimes I want to ensure all my tabs/panes have the new block in which case just killing all of them and restarting would be great.

Oh you may be interested in the "Restart connection" action, added in 1.18, in #15241. (#3726 was this)

@zadjii-msft commented on GitHub (May 10, 2024): > I modify settings and want to reload to ensure changes are loaded... this could be fixed via changing how settings apply to auto-reload like it used to It still does! I suspect though what you're seeing is that when you save a fragment file, the Terminal doesn't hot-reload that. I could have swore there was an issue for that. You can just touch the main terminal settings file to have it hot-reload the fragments too. The terminal will continue to always support hot-reloading its own settings file. I'm not about to break that any time soon 😄 > I modify env vars and want to ensure they are picked up. I understand there is a new setting to open new tabs/panes with the new env block and that is great, but sometimes I want to ensure all my tabs/panes have the new block in which case just killing all of them and restarting would be great. Oh you may be interested in the "Restart connection" action, added in 1.18, in #15241. (#3726 was this)
claunia commented 2026-01-31 07:51:58 +00:00
Author
Owner
Copy Link

@g0t4 commented on GitHub (May 10, 2024):

@zadjii-msft I just tried what you suggested, save the main settings.json and no joe... is it possible if the file is symlinked that it might not detect changes?

@g0t4 commented on GitHub (May 10, 2024): @zadjii-msft I just tried what you suggested, save the main settings.json and no joe... is it possible if the file is symlinked that it might not detect changes?
claunia commented 2026-01-31 07:51:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 10, 2024):

It is 1000% possible. As of #1812, that's by design.

(and it looks like #6209 treads a lot of this same ground)

@zadjii-msft commented on GitHub (May 10, 2024): It is 1000% possible. As of #1812, that's by design. (and it looks like #6209 treads a lot of this same ground)
claunia commented 2026-01-31 07:51:58 +00:00
Author
Owner
Copy Link

@g0t4 commented on GitHub (May 10, 2024):

Alright, I'll close this for now then as the other issue https://github.com/microsoft/terminal/issues/13416 addresses env vars.

@g0t4 commented on GitHub (May 10, 2024): Alright, I'll close this for now then as the other issue https://github.com/microsoft/terminal/issues/13416 addresses env vars.
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-Tag-Fix Needs-Triage
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#21684
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?