starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

unused terminals #12820

New Issue
Closed
opened 2026-01-31 03:25:49 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 03:25:49 +00:00
Owner
Copy Link

Originally created by @bckelley on GitHub (Mar 2, 2021).

Description of the new feature/enhancement

I find it annoying that I can't delete Azure Cloud or WSL terminal or cmd prompt from settings files. I don't even use these programs and I am tired of them clogging up the settings file. Is there some workaround I'm missing, or can there be an update to add this feature?

Proposed technical implementation details (optional)

Originally created by @bckelley on GitHub (Mar 2, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 I find it annoying that I can't delete Azure Cloud or WSL terminal or cmd prompt from settings files. I don't even use these programs and I am tired of them clogging up the settings file. Is there some workaround I'm missing, or can there be an update to add this feature? <!-- 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) <!-- A clear and concise description of what you want to happen. -->
claunia commented 2026-01-31 03:25:50 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Mar 2, 2021):

Use the disabledProfileSources option or hidden in settings.json. These are also in the Settings UI.

@WSLUser commented on GitHub (Mar 2, 2021): Use the `disabledProfileSources` option or `hidden` in settings.json. These are also in the Settings UI.
claunia commented 2026-01-31 03:25:50 +00:00
Author
Owner
Copy Link

@bckelley commented on GitHub (Mar 2, 2021):

I don't even use these programs and I am tired of them clogging up the settings file.

I'm not sure if you actually read this but I clearly state that I DON"T want it clogging up the settings json file

@bckelley commented on GitHub (Mar 2, 2021): > I don't even use these programs and I am tired of them clogging up the settings file. I'm not sure if you actually read this but I clearly state that I DON"T want it clogging up the settings json file
claunia commented 2026-01-31 03:25:50 +00:00
Author
Owner
Copy Link

@Johbii commented on GitHub (Mar 2, 2021):

I don't even use these programs and I am tired of them clogging up the settings file.

I'm not sure if you actually read this but I clearly state that I DON"T want it clogging up the settings json file

Isn't this a very niche point? What is the functional difference in changing this?

@Johbii commented on GitHub (Mar 2, 2021): > > > > I don't even use these programs and I am tired of them clogging up the settings file. > > I'm not sure if you actually read this but I clearly state that I DON"T want it clogging up the settings json file Isn't this a very niche point? What is the functional difference in changing this?
claunia commented 2026-01-31 03:25:51 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 3, 2021):

Well for better or worse, we're moving to use the Settings UI as the default experience. You won't see any JSON if you only use Settings UI 😄

@skyline75489 commented on GitHub (Mar 3, 2021): Well for better or worse, we're moving to use the Settings UI as the default experience. You won't see any JSON if you only use Settings UI 😄
claunia commented 2026-01-31 03:25:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 3, 2021):

Alright so there are a variety of solutions here:

  • For the cloud shell and WSL, you can stop them from being autogenerated with "disabledProfileSources": ["Windows.Terminal.Wsl", "Windows.Terminal.Azure"]. Then you could go ahead and delete the stubs from your settings file.
  • "hidden": true will also work on these profiles, though you specifically don't want them in your json file. We unfortunately need to leave the stubs in there so that we know if a user has seen them or not. Without the stub in your settings file, the WSL auto-detector presumes that this is a distro that you've newly installed.
  • When App state (#8771 and follow-ups) land, it'll be easier to hide/disable these profiles from the settings UI, without cluttering your settings file.
  • For cmd.exe - that's a "built-in" profile, which is in the defaults.json file. If you want to hide that from the new tab dropdown, you'll need to rely on "hidden": true. Sorry about that. I don't think that
{
    "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
 	"hidden": true
}

is too much clutter.

@zadjii-msft commented on GitHub (Mar 3, 2021): Alright so there are a variety of solutions here: * For the cloud shell and WSL, you can stop them from being autogenerated with `"disabledProfileSources": ["Windows.Terminal.Wsl", "Windows.Terminal.Azure"]`. Then you could go ahead and delete the stubs from your settings file. * `"hidden": true` will also work on these profiles, though you specifically don't want them in your json file. We unfortunately need to leave the stubs in there so that we know if a user has seen them or not. Without the stub in your settings file, the WSL auto-detector presumes that this is a distro that you've newly installed. * When App state (#8771 and follow-ups) land, it'll be easier to hide/disable these profiles from the settings UI, without cluttering your settings file. * For cmd.exe - that's a "built-in" profile, which is in the `defaults.json` file. If you want to hide that from the new tab dropdown, you'll need to rely on `"hidden": true`. Sorry about that. I don't think that ```json { "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "hidden": true } ``` is too much clutter.
claunia commented 2026-01-31 03:25:51 +00:00
Author
Owner
Copy Link

@bckelley commented on GitHub (Mar 3, 2021):

thank you @zadjii-msft most helpful! I've looked at the default json file and have noticed powershell is a built-in profile as well, will App state fix it as well?

@bckelley commented on GitHub (Mar 3, 2021): thank you @zadjii-msft most helpful! I've looked at the default json file and have noticed powershell is a built-in profile as well, will App state fix it as well?
claunia commented 2026-01-31 03:25:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 3, 2021):

No, app state isn't planning on addressing the built-in profiles. If you want Command Prompt and Windows PowerShell hidden, then you'll have to live with the 8 lines in your json file 😄

@zadjii-msft commented on GitHub (Mar 3, 2021): No, app state isn't planning on addressing the built-in profiles. If you want Command Prompt **and** Windows PowerShell hidden, then you'll have to live with the 8 lines in your json file 😄
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 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#12820
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?