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

I can't delete default profiles from settings file #7054

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

Originally created by @safern on GitHub (Mar 21, 2020).

Environment

Windows build number:
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable):
Version: 0.10.781.0

Steps to reproduce

Open settings file while the terminal is open.
Remove the last settings profile.
Save the file while terminal is open.
The deleted profile will be added back.

Open settings file.
Remove the last settings profile.
Close terminal.
Save settings file.
Open terminal.
The deleted profile will be added back.

Expected behavior

The settings file doesn't bring back profiles I deleted.

Actual behavior

The profiles I remove they come back when I open the terminal or if I save the file while the terminal is open.

Originally created by @safern on GitHub (Mar 21, 2020). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 ``` Windows Terminal version (if applicable): Version: 0.10.781.0 # Steps to reproduce Open settings file while the terminal is open. Remove the last settings profile. Save the file while terminal is open. The deleted profile will be added back. Open settings file. Remove the last settings profile. Close terminal. Save settings file. Open terminal. The deleted profile will be added back. # Expected behavior The settings file doesn't bring back profiles I deleted. # Actual behavior The profiles I remove they come back when I open the terminal or if I save the file while the terminal is open.
claunia added the Resolution-Duplicate label 2026-01-31 00:53:51 +00:00
claunia commented 2026-01-31 00:53:52 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (Mar 21, 2020):

@safern Which file are you editing? defaults.json or profiles.json ?

@oising commented on GitHub (Mar 21, 2020): @safern Which file are you editing? `defaults.json` or `profiles.json` ?
claunia commented 2026-01-31 00:53:52 +00:00
Author
Owner
Copy Link

@jfowlie commented on GitHub (Mar 22, 2020):

I'm experiencing the same problem -- I am editing the profiles.json file and removing profiles that I don't use, but they come back immediately after closing and restarting the program. My other settings changes in that file appear to be sticking (changing the default profile, and re-ordering the profiles).

@jfowlie commented on GitHub (Mar 22, 2020): I'm experiencing the same problem -- I am editing the profiles.json file and removing profiles that I don't use, but they come back immediately after closing and restarting the program. My other settings changes in that file appear to be sticking (changing the default profile, and re-ordering the profiles).
claunia commented 2026-01-31 00:53:52 +00:00
Author
Owner
Copy Link

@safern commented on GitHub (Mar 24, 2020):

@safern Which file are you editing? defaults.json or profiles.json ?

I'm editing profiles.json. Same experience as @jfowlie above, if I change the order of profiles or add custom settings to any profile, they do stick, but when removing profiles I don't need they come back when saving if the terminal is open or when I open the terminal again.

@safern commented on GitHub (Mar 24, 2020): > @safern Which file are you editing? defaults.json or profiles.json ? I'm editing `profiles.json`. Same experience as @jfowlie above, if I change the order of profiles or add custom settings to any profile, they do stick, but when removing profiles I don't need they come back when saving if the terminal is open or when I open the terminal again.
claunia commented 2026-01-31 00:53:52 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 24, 2020):

/dup #3121 this might be an enlightening read 😄 sorry, we'll work to make sure our documentation is smarter here

@DHowett-MSFT commented on GitHub (Mar 24, 2020): /dup #3121 this might be an enlightening read :smile: sorry, we'll work to make sure our documentation is smarter here
claunia commented 2026-01-31 00:53:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 24, 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 (Mar 24, 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!
claunia commented 2026-01-31 00:53:53 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 24, 2020):

I'm sorry, I meant /dup #3231

@DHowett-MSFT commented on GitHub (Mar 24, 2020): I'm sorry, I meant /dup #3231
claunia commented 2026-01-31 00:53:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 24, 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 (Mar 24, 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!
claunia commented 2026-01-31 00:53:53 +00:00
Author
Owner
Copy Link

@Vaskinn commented on GitHub (Apr 13, 2021):

@DHowett-MSFT It's problematic when bug reports are closed as duplicates of an already closed bug report that has been locked for comments. How are we supposed to provide feedback and suggestions then? I'll just do it here since it seems my best option.

I think this automatic profile generation would be a lot friendlier if the generated profile included a commentthat says something like "This profile generated by ..., to prevent it from being generated again add ... to disabledProfileSources"

@Vaskinn commented on GitHub (Apr 13, 2021): @DHowett-MSFT It's problematic when bug reports are closed as duplicates of an already closed bug report ~~that has been locked for comments~~. How are we supposed to provide feedback and suggestions then? I'll just do it here since it seems my best option. I think this automatic profile generation would be a lot friendlier if the generated profile included a commentthat says something like "This profile generated by ..., to prevent it from being generated again add ... to disabledProfileSources"
claunia commented 2026-01-31 00:53:54 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2021):

To be fair, this was resolved as a duplicate in March last year, and then the linked thread was locked in the following June, so that checks out to me.

I don't disagree that adding the comment might be helpful - though with the Settings UI getting shipped soontm, it's probably easiest to just slap something in the UI, rather than in the file itself 🤔

@zadjii-msft commented on GitHub (Apr 13, 2021): To be fair, this was resolved as a duplicate in March last year, and then the linked thread was locked in the following June, so that checks out to me. I don't disagree that adding the comment might be helpful - though with the Settings UI getting shipped soon<sup>tm</sup>, it's probably easiest to just slap something in the UI, rather than in the file itself 🤔
claunia commented 2026-01-31 00:53:54 +00:00
Author
Owner
Copy Link

@Vaskinn commented on GitHub (Apr 13, 2021):

My mistake, I didn't check the dates properly 👎

@Vaskinn commented on GitHub (Apr 13, 2021): My mistake, I didn't check the dates properly 👎
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 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#7054
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?