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 ability in menu > above settings > reset / refresh settings #8635

New Issue
Closed
opened 2026-01-31 01:34:22 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 01:34:22 +00:00
Owner
Copy Link

Originally created by @Karl-WE on GitHub (May 28, 2020).

Description of the new feature/enhancement

some users likely have very old json files (global / user local) that may cause unnecessary questions or usage concerns.

see #6215 #6216

The root cause was that my json file was very very old and terminal (for good) does not simply upgrade / alter json files with a new version / update via Microsoft Store.

However a new file hits it with this new useful disclaimer in the user json.
My old one did not have this one yet, so I wasn't aware about so many dramatic changes as a casual user of Terminal for my Powershell and cmd.

// This file was initially generated by Windows Terminal 1.0.1401.0
// It should still be usable in newer versions, but newer versions might have additional
// settings, help text, or changes that you will not see unless you clear this file
// and let us generate a new one for you.

Proposed technical implementation details (optional)

If you see the drop down menu please add a new entry that is named like "refresh settings"

include a warning like:

Msgbox:
"Starting over can be a good choice to get easier access to new features and configurable settings"
This will delete all your jsons on next restart of Terminal. For a backup choose Settings before closing the terminal window."

Msgbox: Yes, delete config to latest defaults / Keep current

  • place a trigger file for the yes decision, regenerate all jsons / delete lock files on next start
Originally created by @Karl-WE on GitHub (May 28, 2020). # Description of the new feature/enhancement some users likely have very old json files (global / user local) that may cause unnecessary questions or usage concerns. see #6215 #6216 The root cause was that my json file was very very old and terminal (for good) does not simply upgrade / alter json files with a new version / update via Microsoft Store. However a new file hits it with this new useful disclaimer in the user json. My old one did not have this one yet, so I wasn't aware about so many dramatic changes as a casual user of Terminal for my Powershell and cmd. ``` // This file was initially generated by Windows Terminal 1.0.1401.0 // It should still be usable in newer versions, but newer versions might have additional // settings, help text, or changes that you will not see unless you clear this file // and let us generate a new one for you. ``` # Proposed technical implementation details (optional) If you see the drop down menu please add a new entry that is named like "refresh settings" include a warning like: Msgbox: "Starting over can be a good choice to get easier access to new features and configurable settings" **This will delete all your jsons on next restart of Terminal.** For a backup choose Settings before closing the terminal window." Msgbox: Yes, delete config to latest defaults / Keep current - place a trigger file for the yes decision, regenerate all jsons / delete lock files on next start
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:34:22 +00:00
claunia commented 2026-01-31 01:34:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2020):

Hey so there's already #947 which covers adding this button to the settings UI (#1564), when we eventually get around to the settings UI. I think that's probably a more appropriate place for this button, so I'm gonna close this issue as a dupe. Thanks!

/dup #947

@zadjii-msft commented on GitHub (May 28, 2020): Hey so there's already #947 which covers adding this button to the settings UI (#1564), when we eventually get around to the settings UI. I think that's probably a more appropriate place for this button, so I'm gonna close this issue as a dupe. Thanks! /dup #947
claunia commented 2026-01-31 01:34:23 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 28, 2020):

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!

@ghost commented on GitHub (May 28, 2020): 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!
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#8635
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?