Shortcut to create new window with current profile? Equivalently, clone current tab into new window

[vkoukis]

Thank you for your work on the Windows Terminal so far, it's pretty awesome!

Description of the new feature/enhancement

Support a shortcut to create a new window with current profile / clone current tab into a new window. That is, if the current tab uses my non-default "Debian" profile, pressing this shortcut will open a new window with a single tab of the "Debian" profile.

This would be super useful to enable a window-based approach, with tiled windows, and it would go really well with the "Focus" launch mode. I see this was rationale behind the requests to add the "New Window" shortcut, Ctrl-Shift-N in the first place [#1051, #3144]

Workarounds

I am describing a few workarounds below:

• Ctrl-Shift-N opens a new window, but it always starts with the default profile. I haven't found a way to ask it to use the current profile instead.
• I can use the mouse to Shift-click on a profile from the dropdown menu. Plus, I can open the dropdown menu easily using Ctrl-Shift-Space, but it's not a single keystroke.
• I can run wt.exe -p $WT_PROFILE_ID, and I can also alias this for my shell, alias w="wt.exe -p $WT_PROFILE_ID", but this only works in Linux, and requires I'm at the shell prompt.

It would be awesome to have a single, easy to use keystroke [Alt-F2? :) ] to duplicate the current profile into a new window.

Proposed technical implementation details (optional)

There already is a command to start a new window, newWindow.
https://learn.microsoft.com/en-us/windows/terminal/customize-settings/actions#window-management-commands

It already accepts index and profile arguments, but they are absolute. I haven't found a way to refer to the current index/profile.
Maybe we could extend index and/or profile so -1 means "use the index corresponding to the profile of the current tab".
I'd love any feedback on this, and I would be happy to contribute to the implementation.

[237dmitry]

Support a shortcut to create a new window with current profile

If you did not change windowingBehavior you can create shortcuts for every profile, like this

{"command": {"action": "newWindow","profile": "<profile name> or <guid>"},"keys": "ctrl+alt+0"}

but this only works in Linux

Write function and set alias for it:

[vkoukis]

@237dmitry thank you for your answer. Inline comments follow.

If you did not change windowingBehavior you can create shortcuts for every profile, like this

{"command": {"action": "newWindow","profile": "<profile name> or <guid>"},"keys": "ctrl+alt+0"}

Yes, but this requires pressing a different key combination depending on the current profile, to clone it.
For example:
I have to remember that I'm using the "Debian" profile, so I have to press ctrl-shift-0 o open a new Debian profile.
I have to remember that I'm using the "Ubuntu" profile, so I have to press ctrl-shift-1 to open a new Ubuntu profile.
There is no way to press ctrl-shift-something and have it open a new window for the current profile.

but this only works in Linux

Write function and set alias for it:

I understand this is a Powershell function that runs wt -p $Env:WT_PROFILE_ID. Yes, I can define aliases for all different profiles [a .bat file for Command Prompt, as well...], but it would be much simpler to just support index = -1 or another special value meaning "the current profile" for the newWindow command.

[zadjii-msft]

This request lives in the same nexus as #10232, #12985. (those are about a tab with different NewTerminalArgs, but the same goes for making windows).

• duplicateTab doesn't accept NewTerminalArgs.
• splitPane uses splitMode: duplicate to duplicate the pane, and then accept any additional args as overrides on the current pane's settings.

We basically need a reconciled version of those for newTab and newWindow. Maybe just duplicate: true. Though, there's been debate in the past about "duplicate the current pane as a new tab" vs "duplicate the tree structure of this tab(window) into the new tab(window)". I suspect that the former is easier, and a sensible default for true, and we could add an enum version of duplicate later.

That would effectively deprecate duplicateTab, as that would be a 1-1 alias for newTab(duplicate: true).