Feature Request: Key binding for &#34;New Window&#34; #1406

@zadjii-msft commented on GitHub (May 29, 2019):

Do you possibly mean #653?

@zadjii-msft commented on GitHub (May 29, 2019): Do you possibly mean #653?

claunia commented

@quank123wip commented on GitHub (May 29, 2019):

Do you possibly mean #653?

No, just call a new window,just like konsole

@quank123wip commented on GitHub (May 29, 2019): > Do you possibly mean #653? No, just call a new window,just like konsole

claunia commented

@zadjii-msft commented on GitHub (May 29, 2019):

Oh, so just a keybinding for opening a new window? Yea we should do that.

@zadjii-msft commented on GitHub (May 29, 2019): Oh, so just a keybinding for opening a new window? Yea we should do that.

claunia commented

2026-01-30 22:25:18 +00:00

@DHowett-MSFT commented on GitHub (May 29, 2019):

I've renamed this to capture what I think it means.

@DHowett-MSFT commented on GitHub (May 29, 2019): I've renamed this to capture what I think it means.

claunia commented

@DHowett-MSFT commented on GitHub (May 30, 2019):

Triaged. We need to think about what it means for terminal to have multiple windows. This will also impact how we do tab tearoff.

@DHowett-MSFT commented on GitHub (May 30, 2019): Triaged. We need to think about what it means for terminal to _have_ multiple windows. This will also impact how we do tab tearoff.

claunia commented

2026-01-30 22:25:18 +00:00

@DHowett-MSFT commented on GitHub (Aug 8, 2019):

When we do this, we should consider supporting shift-click on the + button to open a new window.

@DHowett-MSFT commented on GitHub (Aug 8, 2019): When we do this, we should consider supporting shift-click on the `+` button to open a new window.

claunia commented

2026-01-30 22:25:18 +00:00

@quank123wip commented on GitHub (Aug 10, 2019):

When we do this, we should consider supporting shift-click on the + button to open a new window.

Maybe we should provide a setting?

@quank123wip commented on GitHub (Aug 10, 2019): > When we do this, we should consider supporting shift-click on the `+` button to open a new window. Maybe we should provide a setting?

claunia commented

@DHowett-MSFT commented on GitHub (Aug 10, 2019):

Why would that setting be turned off? What’s the alternative scenario?

@DHowett-MSFT commented on GitHub (Aug 10, 2019): Why would that setting be turned off? What’s the alternative scenario?

claunia commented

@ffes commented on GitHub (Aug 27, 2019):

Note that in #2320 I suggested the Shift+Click on an entry in the list of profiles to open a new window as well.

@ffes commented on GitHub (Aug 27, 2019): Note that in #2320 I suggested the `Shift+Click` on an entry in the list of profiles to open a new window as well.

claunia commented

@ffes commented on GitHub (Aug 27, 2019):

Maybe we should provide a setting?

To make a normal click on the button / entry in the list of profiles open a new window and shift-click open a new tab you mean? So swap the behavior.

That could very well become my personal preference 😉

@ffes commented on GitHub (Aug 27, 2019): > Maybe we should provide a setting? To make a normal click on the button / entry in the list of profiles open a new window and shift-click open a new tab you mean? So swap the behavior. That could very well become my personal preference :wink:

claunia commented

@NeKJ commented on GitHub (Oct 11, 2019):

Plus one for this request. It should be implemented for many reasons, but mostly because it will save lots of time for lots of people that are used it to be there. I suggest Ctrl+Shift+n for this.

Just spawn a new instance of WT, that way there will be no worries for window management or tab-tear down, I think this is how all other terminals are doing it.

@NeKJ commented on GitHub (Oct 11, 2019): Plus one for this request. It should be implemented for many reasons, but mostly because it will save lots of time for lots of people that are used it to be there. I suggest Ctrl+Shift+n for this. Just spawn a new instance of WT, that way there will be no worries for window management or tab-tear down, I think this is how all other terminals are doing it.

claunia commented

@quank123wip commented on GitHub (Oct 11, 2019):

Plus one for this request. It should be implemented for many reasons, but mostly because it will save lots of time for lots of people that are used it to be there. I suggest Ctrl+Shift+n for this.

Just spawn a new instance of WT, that way there will be no worries for window management or tab-tear down, I think this is how all other terminals are doing it.

Maybe many people have ever used linux desktop will like using Ctrl+Alt+T?

@quank123wip commented on GitHub (Oct 11, 2019): > Plus one for this request. It should be implemented for many reasons, but mostly because it will save lots of time for lots of people that are used it to be there. I suggest Ctrl+Shift+n for this. > > Just spawn a new instance of WT, that way there will be no worries for window management or tab-tear down, I think this is how all other terminals are doing it. Maybe many people have ever used linux desktop will like using Ctrl+Alt+T?

claunia commented

@SlapBot commented on GitHub (Feb 7, 2020):

+1, Been quite some time in the feature request, has anyone come up with a way to replicate the feature request without downloading/installing any 3rd party library?

I am migrating from Linux to Windows and hotkey to open up new windows terminal is one of my most used shortcuts! Any temporary fix for now to circumvent the problem and open WT doing Ctrl + Alt + T

Btw, I have been doing Win + 1 for now by putting WT as the first app in the taskbar.

@SlapBot commented on GitHub (Feb 7, 2020): +1, Been quite some time in the feature request, has anyone come up with a way to replicate the feature request without downloading/installing any 3rd party library? I am migrating from Linux to Windows and hotkey to open up new windows terminal is one of my most used shortcuts! Any temporary fix for now to circumvent the problem and open WT doing `Ctrl + Alt + T` Btw, I have been doing `Win + 1` for now by putting WT as the first app in the taskbar.

claunia commented

@damnskippy commented on GitHub (Sep 6, 2020):

In case anyone else benefits from this, here's a brilliant workaround suggested by @zadjii-msft here: https://github.com/microsoft/terminal/issues/6200#issuecomment-633996276

@damnskippy commented on GitHub (Sep 6, 2020): In case anyone else benefits from this, here's a brilliant workaround suggested by @zadjii-msft here: https://github.com/microsoft/terminal/issues/6200#issuecomment-633996276

claunia commented

@bschaepper commented on GitHub (Oct 7, 2020):

Building on the solution of @zadjii-msft that @damnskippy referenced, heres how to open a new WSL window:
{ "command": { "action": "newTab", "commandline":"wt.exe new-tab -p <your profile name>" }, "keys": [ "ctrl+shift+n" ] }

@bschaepper commented on GitHub (Oct 7, 2020): Building on the solution of @zadjii-msft that @damnskippy referenced, heres how to open a new WSL window: `{ "command": { "action": "newTab", "commandline":"wt.exe new-tab -p <your profile name>" }, "keys": [ "ctrl+shift+n" ] }`

claunia commented

@quank123wip commented on GitHub (Oct 15, 2020):

I think we need a better solution here. All workarounds are no use when the Windows Terminal isn't running, and for top-down(or drag-down) terminal, we also need a solution to start a new Windows Terminal instance. I think we'd better implement a guard process start when the system boot up. That should be in the Terminal v2.0 Milestone or any other Milestone before this feature.

@quank123wip commented on GitHub (Oct 15, 2020): I think we need a better solution here. All workarounds are no use when the Windows Terminal isn't running, and for top-down(or drag-down) terminal, we also need a solution to start a new Windows Terminal instance. I think we'd better implement a guard process start when the system boot up. That should be in the Terminal v2.0 Milestone or any other Milestone before this feature.

claunia commented

@zadjii-msft commented on GitHub (Oct 15, 2020):

@quank123wip I think what' you're actually looking for is #653

@zadjii-msft commented on GitHub (Oct 15, 2020): @quank123wip I think what' you're actually looking for is #653

claunia commented

@quank123wip commented on GitHub (Oct 17, 2020):

@quank123wip I think what' you're actually looking for is #653

Actually, I think both this feature and that need a same solution about auto start when system boots.

@quank123wip commented on GitHub (Oct 17, 2020): > @quank123wip I think what' you're actually looking for is #653 Actually, I think both this feature and that need a same solution about auto start when system boots.

claunia commented

@zadjii-msft commented on GitHub (Oct 19, 2020):

@quangkieu Hey wadda ya know, that's already a setting we support. See startOnUserLogin

@zadjii-msft commented on GitHub (Oct 19, 2020): @quangkieu Hey wadda ya know, that's already a setting we support. See [`startOnUserLogin`](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/global-settings#launch-on-startup)

claunia commented