starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Duplicate Tab doesn't duplicate split panes #6561

New Issue
Open
opened 2026-01-31 00:41:43 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 00:41:43 +00:00
Owner
Copy Link

Originally created by @keithn on GitHub (Feb 21, 2020).

Steps to reproduce

Create some spit panes in a tab, then ctrl-shift-d to duplicateTab, new tab is a single pane tab.

Expected behavior

new tab is a duplicate of the split paned tab with the same panes

Actual behavior

single pane tab

Originally created by @keithn on GitHub (Feb 21, 2020). # Steps to reproduce Create some spit panes in a tab, then ctrl-shift-d to duplicateTab, new tab is a single pane tab. # Expected behavior new tab is a duplicate of the split paned tab with the same panes # Actual behavior single pane tab
claunia added the Help WantedIssue-TaskProduct-TerminalArea-UserInterface labels 2026-01-31 00:41:43 +00:00
claunia commented 2026-01-31 00:41:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 21, 2020):

I don't hate the idea of adding a setting to the "newTab" ShortcutAction to enable duplicating panes as well. Thanks for the suggestion!

Something like:

{ "command": { "action": "newTab", "duplicatePanes": true }, "keys": ["ctrl+shift+d"] },
@zadjii-msft commented on GitHub (Feb 21, 2020): I don't hate the idea of adding a setting to the "newTab" `ShortcutAction` to enable duplicating panes as well. Thanks for the suggestion! Something like: ```json { "command": { "action": "newTab", "duplicatePanes": true }, "keys": ["ctrl+shift+d"] }, ```
claunia commented 2026-01-31 00:41:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 21, 2020):

I honestly wonder if duplicating a tab should simply always duplicate its panes. After all, not doing so (and terminal randomly selecting one of the panes under the tab) could be viewed as simply incorrect...

@DHowett-MSFT commented on GitHub (Feb 21, 2020): I honestly wonder if duplicating a tab should simply always duplicate its panes. After all, not doing so (and terminal randomly selecting one of the panes under the tab) could be viewed as simply incorrect...
claunia commented 2026-01-31 00:41:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 21, 2020):

Yanking triage in any case: this is a good backlog item, but if somebody wants to work on it we can pull it ahead.

@DHowett-MSFT commented on GitHub (Feb 21, 2020): Yanking triage in any case: this is a good backlog item, but if somebody wants to work on it we can pull it ahead.
claunia commented 2026-01-31 00:41:45 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Oct 16, 2020):

@DHowett-MSFT - I did some short implementation of panes duplication (that almost works, besides setting the focus in the same pane, that I simply cannot get working), but I am just wondering how useful it is when the panes are created in the initial state (e.g. default directory).

@Don-Vito commented on GitHub (Oct 16, 2020): @DHowett-MSFT - I did some short implementation of panes duplication (that almost works, besides setting the focus in the same pane, that I simply cannot get working), but I am just wondering how useful it is when the panes are created in the initial state (e.g. default directory).
claunia commented 2026-01-31 00:41:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 9, 2020):

Maybe it's valuable to do even without the path preservation now, so that when #3158 / #8166 / whatever it ends up being does land, then the path duplication will just start working for duplicated tabs as well.

Personally, I'm the kind of user where I set up each profile's startingDirectory to the root of a project, and typically I stay in the root of each project, so duplicating a bunch of panes that are all in that directory already doesn't seem like a bad thing to me ☺️

@zadjii-msft commented on GitHub (Nov 9, 2020): Maybe it's valuable to do even without the path preservation now, so that when #3158 / #8166 / whatever it ends up being _does_ land, then the path duplication will just start working for duplicated tabs as well. Personally, I'm the kind of user where I set up each profile's `startingDirectory` to the root of a project, and typically I stay in the root of each project, so duplicating a bunch of panes that are all in that directory already doesn't seem like a bad thing to me ☺️
claunia commented 2026-01-31 00:41:46 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Nov 9, 2020):

@zadjii-msft - I will try to push it then.. hopefully this week / weekend.

@Don-Vito commented on GitHub (Nov 9, 2020): @zadjii-msft - I will try to push it then.. hopefully this week / weekend.
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-UserInterface Help Wanted Issue-Task 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#6561
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?