Terminal: Split Pane with same Profile

Created on 26 Apr 2020  路  3Comments  路  Source: microsoft/terminal

Description of the new mini-feature

For what I know it is only possible to split the pane with the default profile or with a selected profile, e.g. always the 2nd profile. I would like to suggest an option to define a shortcut for splitting the pane with the same profile as the profile currently opened. This would come handy because the is the functionality I expected in the first place.

Issue-Feature Resolution-Duplicate

Most helpful comment

Thanks for the suggestion! This is such a good idea that _we already implemented it_ 馃槅

You can achieve what your looking for with a keybinding like the following:

        { "command": { "action": "splitPane", "split":"auto", "splitMode": "duplicate" }, "keys": [ "ctrl+alt+t" ] },

"splitMode": "duplicate" tells the keybinding to create a pane with the same profile as the current pane.

"split":"auto" tells the binding to create a pane in whichever direction results in the pane being _larger_. If the Terminal is currently wider than it is tall, then the split will be vertical (think "[ | ]").

/dup #1756

All 3 comments

Thanks for the suggestion! This is such a good idea that _we already implemented it_ 馃槅

You can achieve what your looking for with a keybinding like the following:

        { "command": { "action": "splitPane", "split":"auto", "splitMode": "duplicate" }, "keys": [ "ctrl+alt+t" ] },

"splitMode": "duplicate" tells the keybinding to create a pane with the same profile as the current pane.

"split":"auto" tells the binding to create a pane in whichever direction results in the pane being _larger_. If the Terminal is currently wider than it is tall, then the split will be vertical (think "[ | ]").

/dup #1756

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!

Okay sorry for bothering you 馃ゴ. I've should have looked deeper for it, I must have overlook it in default.json. But cool to have it and thank you for your work 鉁岋笍

Was this page helpful?
0 / 5 - 0 ratings