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

Add nested commands to the Command Palette #5614

New Issue
Closed
opened 2026-01-31 00:17:30 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 00:17:30 +00:00
Owner
Copy Link

Originally created by @zadjii-msft on GitHub (Dec 17, 2019).

The initial design of the command palette only covers singular commands, but includes a follow-up to support nesting commands. This way, all the commands don't appear in the menu straight away. Instead, the user must first select the parent command, to be given the sub-list.

We should support this.

Originally created by @zadjii-msft on GitHub (Dec 17, 2019). The initial design of the command palette only covers singular commands, but includes a follow-up to support nesting commands. This way, all the commands don't appear in the menu straight away. Instead, the user must first select the parent command, to be given the sub-list. We should support this.
claunia added the Resolution-Fix-CommittedArea-SettingsIssue-TaskProduct-Terminal labels 2026-01-31 00:17:30 +00:00
claunia commented 2026-01-31 00:17:31 +00:00
Author
Owner
Copy Link

@cryptworks commented on GitHub (Apr 16, 2020):

I would +1 to this. Recently working with the terminal profiles.json I was having fun with calling directly to the native windows SSH "ssh.exe user@addr" as its own profile. The ability to make a manuitem to call to a separate config as its own menu entry would be tremendous. Even supporting a nested entry of ssh x@x calls with a singular master config entry would be great.

@cryptworks commented on GitHub (Apr 16, 2020): I would +1 to this. Recently working with the terminal profiles.json I was having fun with calling directly to the native windows SSH "ssh.exe user@addr" as its own profile. The ability to make a manuitem to call to a separate config as its own menu entry would be tremendous. Even supporting a nested entry of ssh x@x calls with a singular master config entry would be great.
claunia commented 2026-01-31 00:17:31 +00:00
Author
Owner
Copy Link

@giggio commented on GitHub (Aug 17, 2020):

@zadjii-msft How do we add those nested commands? Is there a commands.json or something like that? I couldn't find it. Or is it on the settings file? If it is, I couldn't find it on schema.

Or is it not supposed to be user customizable?

@giggio commented on GitHub (Aug 17, 2020): @zadjii-msft How do we add those nested commands? Is there a `commands.json` or something like that? I couldn't find it. Or is it on the settings file? If it is, I couldn't find it on schema. Or is it not supposed to be user customizable?
claunia commented 2026-01-31 00:17:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 17, 2020):

@giggio If you're using a build that includes #6856, you can do something like the following:

        {
            "name": "Split Pane...",
            "commands": [
                {
                    "iterateOn": "profiles",
                    "name": "Split with ${profile.name}...",
                    "commands": [
                        { "command": { "action": "splitPane", "profile": "${profile.name}", "split": "auto" } },
                        { "command": { "action": "splitPane", "profile": "${profile.name}", "split": "vertical" } },
                        { "command": { "action": "splitPane", "profile": "${profile.name}", "split": "horizontal" } }
                    ]
                }
            ]
        },

Just throw that into your keybindings, and that should work.

@zadjii-msft commented on GitHub (Aug 17, 2020): @giggio If you're using a build that includes #6856, you can do something like the following: ```json { "name": "Split Pane...", "commands": [ { "iterateOn": "profiles", "name": "Split with ${profile.name}...", "commands": [ { "command": { "action": "splitPane", "profile": "${profile.name}", "split": "auto" } }, { "command": { "action": "splitPane", "profile": "${profile.name}", "split": "vertical" } }, { "command": { "action": "splitPane", "profile": "${profile.name}", "split": "horizontal" } } ] } ] }, ``` Just throw that into your `keybindings`, and that should work.
claunia commented 2026-01-31 00:17:31 +00:00
Author
Owner
Copy Link

@giggio commented on GitHub (Aug 17, 2020):

Perfect, it works! I was not sure where to put it. There should be an issue to update the schema.

@giggio commented on GitHub (Aug 17, 2020): Perfect, it works! I was not sure where to put it. There should be an issue to update the schema.
claunia commented 2026-01-31 00:17:32 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 17, 2020):

@giggio I'm purposely not updating the docs until we feel it's ready for general adoption 😉

The docs will probably be updated as a part of #7174

@zadjii-msft commented on GitHub (Aug 17, 2020): @giggio I'm purposely not updating the docs until we feel it's ready for general adoption 😉 The docs will probably be updated as a part of #7174
claunia commented 2026-01-31 00:17:32 +00:00
Author
Owner
Copy Link

@giggio commented on GitHub (Aug 17, 2020):

Not the docs, the schema: https://github.com/microsoft/terminal/blob/master/doc/cascadia/profiles.schema.json

@giggio commented on GitHub (Aug 17, 2020): Not the docs, the schema: https://github.com/microsoft/terminal/blob/master/doc/cascadia/profiles.schema.json
claunia commented 2026-01-31 00:17:32 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 17, 2020):

Sorry, in my head, the schema is part of the docs. I get how that's confusing 😛

@zadjii-msft commented on GitHub (Aug 17, 2020): Sorry, in my head, the schema is part of the docs. I get how that's confusing 😛
claunia commented 2026-01-31 00:17:32 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 26, 2020):

:tada:This issue was addressed in #6856, which has now been successfully released as Windows Terminal Preview v1.3.2382.0.🎉

Handy links:

@ghost commented on GitHub (Aug 26, 2020): :tada:This issue was addressed in #6856, which has now been successfully released as `Windows Terminal Preview v1.3.2382.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.3.2382.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-Settings Issue-Task Product-Terminal Resolution-Fix-Committed
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#5614
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?