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

Splitting a tab should offer profiles like it used to #22063

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

Originally created by @inosik on GitHub (Aug 8, 2024).

Description of the new feature/enhancement

The "Split pane" command used to have a submenu, where you could select the profile for the new pane:

WindowsTerminal_2024-08-08_15-32-52

Right now I have no idea how to create a new pane using a profile that is not the default one.

Originally created by @inosik on GitHub (Aug 8, 2024). # Description of the new feature/enhancement The "Split pane" command used to have a submenu, where you could select the profile for the new pane: ![WindowsTerminal_2024-08-08_15-32-52](https://github.com/user-attachments/assets/46468969-0399-40b5-b723-1ae3d33dbbad) Right now I have no idea how to create a new pane using a profile that is not the default one.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 08:02:27 +00:00
claunia commented 2026-01-31 08:02:28 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Aug 14, 2024):

Oh no... This is another manifestation of #17294.

I'm guessing you added a plain "command": "splitPane" to your settings.json. We expose that as Split pane in the command palette.

In #16886, the key for the nested action got renamed from Split Pane... to Split pane. This accidentally caused a collision because now you have two actions with the same name! The settings model then prefers your action over the one defined in defaults.json, thus completely hiding the nested version.

I'm marking this a /dup of #17294 and reverting the ... changes in the names. That should make these come back 😊

@carlos-zamora commented on GitHub (Aug 14, 2024): Oh no... This is another manifestation of #17294. I'm guessing you added a plain `"command": "splitPane"` to your settings.json. We expose that as `Split pane` in the command palette. In #16886, the key for the nested action got renamed from `Split Pane...` to `Split pane`. This accidentally caused a collision because now you have two actions with the same name! The settings model then prefers _your_ action over the one defined in defaults.json, thus completely hiding the nested version. I'm marking this a /dup of #17294 and reverting the `...` changes in the names. That should make these come back 😊
claunia commented 2026-01-31 08:02:28 +00:00
Author
Owner
Copy Link

@inosik commented on GitHub (Aug 16, 2024):

I'm guessing you added a plain "command": "splitPane" to your settings.json

You're right, there was an action that was bound to this command. I'm not aware of ever adding it though.

However, I removed it and the submenu is back, thanks!

@inosik commented on GitHub (Aug 16, 2024): > I'm guessing you added a plain "command": "splitPane" to your settings.json You're right, there was an action that was bound to this command. I'm not aware of ever adding it though. However, I removed it and the submenu is back, thanks!
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#22063
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?