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

Prevent Windows Terminal from (needlessly) changing settings.json #19149

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

Originally created by @skrysm on GitHub (Dec 27, 2022).

Discussed in https://github.com/microsoft/terminal/discussions/14380

Originally posted by skrysmanski November 13, 2022
I have a "hand crafted" settings.json since the earliest days of Windows Terminal. I have this file under version control (via Git).

The current version of Windows Terminal (1.15) seems to overwrite/rewrite my settings.json every time Windows Terminal is opened/closed.

Is there any way to prevent Windows Terminal from doing this?

It is, of course, okay that WT rewrites the file if I use the settings UI to change some settings. But it shouldn't do this if I don't use the UI.

Originally created by @skrysm on GitHub (Dec 27, 2022). ### Discussed in https://github.com/microsoft/terminal/discussions/14380 <div type='discussions-op-text'> <sup>Originally posted by **skrysmanski** November 13, 2022</sup> I have a "hand crafted" `settings.json` since the earliest days of Windows Terminal. I have this file under version control (via Git). The current version of Windows Terminal (1.15) seems to overwrite/rewrite my `settings.json` every time Windows Terminal is opened/closed. Is there any way to prevent Windows Terminal from doing this? It is, of course, okay that WT rewrites the file if I use the settings UI to change some settings. But it shouldn't do this if I don't use the UI.</div>
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 06:35:08 +00:00
claunia commented 2026-01-31 06:35:09 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Dec 30, 2022):

In most cases it shouldn't be updating your settings.json file as far as I can tell. Outside of you actually editing something in the Settings GUI, the only other scenarios in which it might save of its own accord are when a dynamic profile is generated, or when fixing up profiles where the command line is something like cmd.exe or powershell.exe (i.e. without a path). Is it possible that the latter case applies to you?

It's also worth mentioning that there is an open issue to try and make it do a better job of preserving the original json structure when rewriting the settings (see #8991). Hopefully then it would be less of an issue for you when the terminal does need to force an update for some reason.

@j4james commented on GitHub (Dec 30, 2022): In most cases it shouldn't be updating your `settings.json` file as far as I can tell. Outside of you actually editing something in the Settings GUI, the only other scenarios in which it might save of its own accord are when a dynamic profile is generated, or when fixing up profiles where the command line is something like `cmd.exe` or `powershell.exe` (i.e. without a path). Is it possible that the latter case applies to you? It's also worth mentioning that there is an open issue to try and make it do a better job of preserving the original json structure when rewriting the settings (see #8991). Hopefully then it would be less of an issue for you when the terminal does need to force an update for some reason.
claunia commented 2026-01-31 06:35:09 +00:00
Author
Owner
Copy Link

@skrysm commented on GitHub (Dec 30, 2022):

the only other scenarios in which it might save of its own accord are when a dynamic profile is generated, or when fixing up profiles where the command line is something like cmd.exe or powershell.exe (i.e. without a path). Is it possible that the latter case applies to you?

Yes, this was exactly the case and your answer is exactly what I was looking for. Thank you. :)

@skrysm commented on GitHub (Dec 30, 2022): > the only other scenarios in which it might save of its own accord are when a dynamic profile is generated, or when fixing up profiles where the command line is something like `cmd.exe` or `powershell.exe` (i.e. without a path). Is it possible that the latter case applies to you? Yes, this was exactly the case and your answer is exactly what I was looking for. Thank you. :)
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-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#19149
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?