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

Make the "hide profile from dropdown" profile setting more easily discoverable #23955

New Issue
Open
opened 2026-01-31 08:57:12 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:57:12 +00:00
Owner
Copy Link

Originally created by @Vap0r1ze on GitHub (Jan 12, 2026).

Description of the new feature

I rarely open my Windows Terminal settings, but when I do it's very frequently to edit what profiles are in the dropdown. Almost everytime I'm like scanning the profile settings looking for a "Show" option or "Enabled/Disabled" option. Eventually the lengthy "Hide profile from dropdown" catches my eye, but it always takes a while because it's at the bottom of all the other appearence options.

Mentally I consider that option as like one of the "main" options of not the main option, and I think it should be a little more easy to change at just a glance.

Proposed technical implementation details

A few ideas, ideally could implement all of them:

  • A clickable toggle button that switches between an Eye icon and a, placed either within the profile's sidebar row or next to the Profile Settings page title.
  • Move the setting to the top of the settings list.
  • Rename to just "Hide profile" so it can be more easily while skimming.
  • (Way more work) Adding icons to all of the profile settings to aid skimming, this alone could help but doing the above three is better IMO.
Originally created by @Vap0r1ze on GitHub (Jan 12, 2026). ### Description of the new feature I rarely open my Windows Terminal settings, but when I do it's very frequently to edit what profiles are in the dropdown. Almost everytime I'm like scanning the profile settings looking for a "Show" option or "Enabled/Disabled" option. Eventually the lengthy "Hide profile from dropdown" catches my eye, but it always takes a while because it's at the bottom of all the other appearence options. Mentally I consider that option as like one of the "main" options of not *the* main option, and I think it should be a little more easy to change at just a glance. ### Proposed technical implementation details A few ideas, ideally could implement all of them: - A clickable toggle button that switches between an Eye icon and a, placed either within the profile's sidebar row or next to the Profile Settings page title. - Move the setting to the top of the settings list. - Rename to just "Hide profile" so it can be more easily while skimming. - (Way more work) Adding icons to all of the profile settings to aid skimming, this alone could help but doing the above three is better IMO.
claunia added the Issue-FeatureProduct-TerminalArea-SettingsUI labels 2026-01-31 08:57:13 +00:00
claunia commented 2026-01-31 08:57:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 12, 2026):

FWIW - this is perhaps a bit more off the beaten track, but if you want tighter control over the content of your dropdown then the New Tab Menu section will give it to you. Removing the "remaining profiles" entry or putting it into a folder will prevent Terminal from showing any profiles you have not selected.

@DHowett commented on GitHub (Jan 12, 2026): FWIW - this is perhaps a bit more off the beaten track, but if you want tighter control over the content of your dropdown then the `New Tab Menu` section will give it to you. Removing the "remaining profiles" entry or putting it into a folder will prevent Terminal from showing _any_ profiles you have not selected.
claunia commented 2026-01-31 08:57:15 +00:00
Author
Owner
Copy Link

@Vap0r1ze commented on GitHub (Jan 12, 2026):

@DHowett I'll say that is a pretty decent alternative, but I do like how the regular profile system auto-detects new installed shells and I really prefer the regular system for ease. Tbh the feature request is all about easy, accessibility, & UX

@Vap0r1ze commented on GitHub (Jan 12, 2026): @DHowett I'll say that is a pretty decent alternative, but I do like how the regular profile system auto-detects new installed shells and I really prefer the regular system for ease. Tbh the feature request is all about easy, accessibility, & UX
claunia commented 2026-01-31 08:57:15 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 15, 2026):

You're totally right. I don't mean that in an "I am a large language model" sort of way (ew).

There's a few things in this bucket that I think we need to resolve, and unfortunately I feel like they're all vaguely the same thing. Profile Ordering and Management.

I'm leaving this brain dump here and assigning myself as a signpost to do a better job cleaning it up later.

  • Profile Index is based on order in the literal profile list, minus hidden profiles
    • We have some other bugs about this; I should go find them.
    • Maybe we should construct the NTM first, and then go through it afterwards and assign the profiles an imputed index.
      • There are maybe 3 people in the world (I hope-guess) that both use NTM customization and have memorized the number associated with each profile. If we do this, we break them.
  • There are two ways to hide profiles, either in newTabMenu by omission only or in the profile itself.
    • We cannot build a feature on newTabMenu alone, because that ignores the reality that we have Command Palette and Jump List support. So, hidden needs to remain. It is also the way that Visual Studio (et al) can customize how their applications appear without creating a profile for the user to see/be annoyed with (like VSDebugConsole).
  • We're working on redesigning the settings UI and are probably making profiles a top-level page rather than making each one a navigation item.
    • This gives us a better place to put an eyeball button, and reordering handles.
@DHowett commented on GitHub (Jan 15, 2026): You're totally right. I don't mean that in an "I am a large language model" sort of way (ew). There's a few things in this bucket that I think we need to resolve, and unfortunately I feel like they're all vaguely the same thing. Profile Ordering and Management. I'm leaving this brain dump here and assigning myself as a signpost to do a better job cleaning it up later. - Profile Index is based on order in the literal profile list, minus hidden profiles - We have some other bugs about this; I should go find them. - Maybe we should construct the NTM first, and then go through it _afterwards_ and assign the profiles an imputed index. - There are maybe 3 people in the world (I hope-guess) that both use NTM customization _and_ have memorized the number associated with each profile. If we do this, we break them. - There are two ways to hide profiles, either in `newTabMenu` _by omission only_ or in the profile itself. - We cannot build a feature on `newTabMenu` alone, because that ignores the reality that we have Command Palette and Jump List support. So, `hidden` needs to remain. It is also the way that Visual Studio (et al) can customize how their applications appear without creating a profile for the user to see/be annoyed with (like `VSDebugConsole`). - We're working on redesigning the settings UI and are probably making profiles a top-level page rather than making each one a navigation item. - This gives us a better place to put an eyeball button, and reordering handles.
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 Area-SettingsUI Issue-Feature Product-Terminal
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#23955
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?