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

Organise profiles in folders in the dropdown #11945

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

Originally created by @tforster on GitHub (Jan 3, 2021).

Description of the new feature/enhancement

The ability to specify optional folder names for profiles in the profiles dropdown menu.

I am a consultant that works on multiple projects for multiple clients. I typically create a per-client/per-project directory structure in my filesystem and corresponding Terminal profiles rooted to each location. My dropdown list is growing and becoming long-scrolling/unusable. It would be great to have the option to drop down a list of folders, with a rollover/click on each folder revealing a cascading dropdown of profiles.

Proposed technical implementation details (optional)

I see two potential methods of organisation:

  1. Add a new and optional "folder" property in the profile schema. When detected the UI creates the corresponding value as the dropdown entry and groups all profiles sharing that property value below the new entry.

  2. Introduce support for a profile hierarchy along the lines of

    profiles/{group-name}/default
profiles/{group-name/list

    along with the existing

    profiles/default
profiles/list

    This would allow profiles below any optionally created {profile-name} to be grouped and displayed in the dropdown while also providing a more intuitive hierarchy for organisation and setting of default values.

Originally created by @tforster on GitHub (Jan 3, 2021). # Description of the new feature/enhancement The ability to specify optional folder names for profiles in the profiles dropdown menu. I am a consultant that works on multiple projects for multiple clients. I typically create a per-client/per-project directory structure in my filesystem and corresponding Terminal profiles rooted to each location. My dropdown list is growing and becoming long-scrolling/unusable. It would be great to have the option to drop down a list of folders, with a rollover/click on each folder revealing a cascading dropdown of profiles. # Proposed technical implementation details (optional) I see two potential methods of organisation: 1. Add a new and optional "folder" property in the profile schema. When detected the UI creates the corresponding value as the dropdown entry and groups all profiles sharing that property value below the new entry. 1. Introduce support for a profile hierarchy along the lines of ``` profiles/{group-name}/default profiles/{group-name/list ``` along with the existing ``` profiles/default profiles/list ``` This would allow profiles below any optionally created {profile-name} to be grouped and displayed in the dropdown while also providing a more intuitive hierarchy for organisation and setting of default values.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 03:01:51 +00:00
claunia commented 2026-01-31 03:01:52 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 4, 2021):

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #1571 for more discussion.

/dup #1571

@zadjii-msft commented on GitHub (Jan 4, 2021): Thanks for the suggestion! Please make sure to [search for duplicates](https://github.com/microsoft/terminal/issues?q=is%3Aissue+profiles+folder+is%3Aclosed) when filing new issues. This is already being tracked by another issue on our repo - please refer to #1571 for more discussion. /dup #1571
claunia commented 2026-01-31 03:01:52 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 4, 2021):

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 (Jan 4, 2021): 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#11945
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?