Add per-window-name global settings #13669

@DHowett commented on GitHub (Apr 29, 2021):

This would make it so much easier for people to have "work profiles" they come into in the morning
Specialization for quake that isn't special
GlobalAppSettings is already inheritable (!)

Bad points:

what if you rename a window

@DHowett commented on GitHub (Apr 29, 2021): 1. This would make it so much easier for people to have "work profiles" they come into in the morning 2. Specialization for quake that isn't special 3. GlobalAppSettings is already inheritable (!) Bad points: 1. what if you rename a window

claunia commented

@dag03tsc commented on GitHub (May 31, 2021):

I agree this could be pretty useful indeed. Meanwhile, if anyone needs it, I've managed to alter the behavior of the _quake window with this setting:

"startupActions": "wt -w _quake sp -H -p CMD -s .666 \\; sp -H -p UBUNTU -s .5"

The above is just an example of a "quaked" 3-pane symmetric vertical arrange. It's a "hackity-hack" bypass, 'cause I'm just using a legit functionality for something it wasn't designed to, but I'll try to explain its two key points.

First point, if wt -w _quake is the first subcommand provided, it replaces the initially launched window with a "Quake Mode" enabled one; otherwise, it opens an independent one.

Second point, there's a huge difference between writing semicolons ; or escaped semicolons \\;, and the arranging of commands is very important; all subcommands before wt -w _quake are applied within the initially launched window and must be preceded by unescaped semicolons ;, while all subcommands after wt -w _quake are applied within the new "quaked" window and must be preceded by escaped semicolons \\; in order to bypass the initially launched window parsing.

As an example, let's say you want to launch two separate windows with a 2-pane horizontal arrange (PWSH and CMD): a "quaked" one and a "standard" one. If your default profile is PWSH, then you'd write the next setting:

"startupActions": "sp -V -p CMD -s .5 ; wt -w _quake \\; sp -V -p CMD -s .5"

I hope someone finds it useful.

BTW, congratulations! WT is awesome and I really like where it is heading by becoming the Isildur's Bane of all terminals! 🥇

@dag03tsc commented on GitHub (May 31, 2021): I agree this could be pretty useful indeed. Meanwhile, if anyone needs it, I've managed to alter the behavior of the `_quake` window with this setting: `"startupActions": "wt -w _quake sp -H -p CMD -s .666 \\; sp -H -p UBUNTU -s .5"` The above is just an example of a "quaked" 3-pane symmetric vertical arrange. It's a "hackity-hack" bypass, 'cause I'm just using a legit functionality for something it wasn't designed to, but I'll try to explain its two key points. First point, if `wt -w _quake` is the first subcommand provided, it replaces the initially launched window with a "Quake Mode" enabled one; otherwise, it opens an independent one. Second point, there's a huge difference between writing semicolons ` ; ` or escaped semicolons ` \\; `, and the arranging of commands is very important; all subcommands before `wt -w _quake` are applied within the initially launched window and must be preceded by unescaped semicolons ` ; `, while all subcommands after `wt -w _quake` are applied within the new "quaked" window and must be preceded by escaped semicolons ` \\; ` in order to bypass the initially launched window parsing. As an example, let's say you want to launch two separate windows with a 2-pane horizontal arrange (PWSH and CMD): a "quaked" one and a "standard" one. If your default profile is PWSH, then you'd write the next setting: `"startupActions": "sp -V -p CMD -s .5 ; wt -w _quake \\; sp -V -p CMD -s .5"` I hope someone finds it useful. BTW, congratulations! WT is awesome and I really like where it is heading by becoming the Isildur's Bane of all terminals! 🥇

claunia commented

@dag03tsc commented on GitHub (Jun 1, 2021):

@zadjii-msft, I list some additional properties from #10279 that could be useful inside each window entity, along with a short explanation.

"tabs": {
  "name": string;
  "index": number;
  "panes": {
    "index": number;
    "profile": string;
    "size": number;
    "split": string;
    "splitMode": string;
  }[];
}[];
"defaultTab": string;

The goal of tabs is to allow the auto-initialization of multiple tabs and panes and parameterize its behavior.

The property name should be any kind of unique identifier for the tab.
It'd mainly be used by the defaultTab property pairing process but it could also be used with a switchToTab action keybinding.

The property index must decide the order of creation, both for tabs and panes.

The goal of defaultTab is to allow the customization of the initially selected tab.
In other words, once all tabs have been initialized, automatically switch to the tab with name equal to defaultTab.
If defaultTab is undefined, fallback to the last or first one.

I think that profile, size, split and splitMode properties details are quite self-explanatory from the Panes doc but I'll be glad to add its details too if needed.

@dag03tsc commented on GitHub (Jun 1, 2021): @zadjii-msft, I list some additional properties from #10279 that could be useful inside each window entity, along with a short explanation. "tabs": { "name": string; "index": number; "panes": { "index": number; "profile": string; "size": number; "split": string; "splitMode": string; }[]; }[]; "defaultTab": string; The goal of `tabs` is to allow the auto-initialization of multiple tabs and panes and parameterize its behavior. The property `name` should be any kind of unique identifier for the tab. It'd mainly be used by the `defaultTab` property pairing process but it could also be used with a `switchToTab` action keybinding. The property `index` must decide the order of creation, both for tabs and panes. The goal of `defaultTab` is to allow the customization of the initially selected tab. In other words, once all tabs have been initialized, automatically switch to the tab with `name` equal to `defaultTab`. If `defaultTab` is undefined, fallback to the last or first one. I think that `profile`, `size`, `split` and `splitMode` properties details are quite self-explanatory from the [Panes doc](https://docs.microsoft.com/en-us/windows/terminal/panes#customizing-panes-using-key-bindings) but I'll be glad to add its details too if needed.

claunia commented

@jhhcs commented on GitHub (Jul 22, 2021):

Hey everyone, I found this thread while intending to open a feature request for the Quake mode window, which I will just leave here as a user story.

I am using the FAR manager inside Windows terminal and as a FAR user, I would like to be able to configure the Quake mode window so that it covers the entire screen. I currently have ConEmu setup in this exact way; it allows me to switch between using FAR and other windowed applications very quickly and efficiently.

@jhhcs commented on GitHub (Jul 22, 2021): Hey everyone, I found this thread while intending to open a feature request for the Quake mode window, which I will just leave here as a user story. I am using the FAR manager inside Windows terminal and as a FAR user, I would like to be able to configure the Quake mode window so that it covers the entire screen. I currently have ConEmu setup in this exact way; it allows me to switch between using FAR and other windowed applications very quickly and efficiently.

claunia commented

@zadjii-msft commented on GitHub (Jul 22, 2021):

@jhhcs FYI you don't need to use the quakeMode action to summon the window - you could always just configure the Terminal to launch in fullscreen mode, and rebind win+` to a plain old globalSummon action.

@zadjii-msft commented on GitHub (Jul 22, 2021): @jhhcs FYI you don't need to use the `quakeMode` action to summon the window - you could always just configure the Terminal to launch in fullscreen mode, and rebind <kbd>win+\`</kbd> to a plain old [`globalSummon`](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#global-summon) action.

claunia commented

@jhhcs commented on GitHub (Jul 23, 2021):

Oh thank you for that hint, yes that works quite nicely. I then discovered that toggling fullscreen with Alt+Enter can also be used to switch the Quake window to full screen as an alternative solution to my problem.

@jhhcs commented on GitHub (Jul 23, 2021): Oh thank you for that hint, yes that works quite nicely. I then discovered that toggling fullscreen with <kbd>Alt</kbd>+<kbd>Enter</kbd> can also be used to switch the Quake window to full screen as an alternative solution to my problem.

claunia commented

@rnett commented on GitHub (Sep 25, 2021):

User story:
I'd like to be able to have one quake window for WSL ZSH, and another for Powershell. This currently does not seem to be possible.

@rnett commented on GitHub (Sep 25, 2021): User story: I'd like to be able to have one quake window for WSL ZSH, and another for Powershell. This currently does not seem to be possible.

claunia commented

2026-01-31 03:48:58 +00:00

@zadjii-msft commented on GitHub (Sep 27, 2021):

@rnett For now, you could always just give the two windows different names, and bind two separate globalSummon actions for those different names. You'd be able to get the dropdown on each now, but not necessarily the "snap to the top half" behavior.

@zadjii-msft commented on GitHub (Sep 27, 2021): @rnett For now, you could always just give the two windows different names, and bind two separate `globalSummon` actions for those different names. You'd be able to get the dropdown on each now, but not necessarily the "snap to the top half" behavior.

claunia commented

@si-kotic commented on GitHub (Jan 22, 2022):

With regards to tabs in Quake mode, that's what brought me here. Unlike the OP of #11085 I would prefer them on the bottom of the window to the top. Making this configurable would make sense to me, as would being able to toggle them on and off both as a default setting and also during a session.

EDIT: I just accidentally discovered that, if I hold Ctrl while tabbing, I get a vertical list of open tabs. This mostly solves my issue, good work. Is there a similar way of seeing the list of profiles when you're launching a new one?

EDIT AGAIN: I've answered my own question; Ctrl+Shift+Space brings up the profiles list.

@si-kotic commented on GitHub (Jan 22, 2022): With regards to tabs in Quake mode, that's what brought me here. Unlike the OP of #11085 I would prefer them on the bottom of the window to the top. Making this configurable would make sense to me, as would being able to toggle them on and off both as a default setting and also during a session. EDIT: I just accidentally discovered that, if I hold Ctrl while tabbing, I get a vertical list of open tabs. This mostly solves my issue, good work. Is there a similar way of seeing the list of profiles when you're launching a new one? EDIT AGAIN: I've answered my own question; Ctrl+Shift+Space brings up the profiles list.

claunia commented

2026-01-31 03:48:58 +00:00

@zadjii-msft commented on GitHub (Jan 24, 2022):

@si-kotic you may also be interested in following https://github.com/microsoft/terminal/issues/835

@zadjii-msft commented on GitHub (Jan 24, 2022): @si-kotic you may also be interested in following https://github.com/microsoft/terminal/issues/835

claunia commented

2026-01-31 03:48:58 +00:00

@xorinzor commented on GitHub (Jan 31, 2023):

Any updates on this? Having to toggle focus mode manually every time Quake mode starts is quite annoying.
Feels like this issue is trying to bundle too many separate issues into 1 fix.

Sure, profiles would be nice, but that's more of a "feature" then a bugfix.

@xorinzor commented on GitHub (Jan 31, 2023): Any updates on this? Having to toggle focus mode manually every time Quake mode starts is quite annoying. Feels like this issue is trying to bundle too many separate issues into 1 fix. Sure, profiles would be nice, but that's more of a "feature" then a bugfix.

claunia commented

@markusdd commented on GitHub (Feb 1, 2023):

yes I am confused why I got redirected here.
This is a super simple request: launch a quake window with focus mode disabled. can't be done apparently, or does anyone have a solution?

I am not intesred in any of the other things being discussed, but the original ticket redirects here.

There is a -f switch to toggle focus mode on, why isn't there one to keep it off?

@markusdd commented on GitHub (Feb 1, 2023): yes I am confused why I got redirected here. This is a super simple request: launch a quake window with focus mode disabled. can't be done apparently, or does anyone have a solution? I am not intesred in any of the other things being discussed, but the original ticket redirects here. There is a -f switch to toggle focus mode on, why isn't there one to keep it off?

claunia commented

@zadjii-msft commented on GitHub (Sep 14, 2023):

Alright, I'm calling it for this hackathon, but progress notes from the week:

Latest branch was: dev/migrie/fhl-fall-2023/11162-quake-III-arena

Sample JSON

{
    "name": "_quake",
    "defaultProfile": "haunter.gif",
    "dockWindow": {
        "side": "bottom",
        "width": 0.3,
        "height": 0.75
    },
    "centerOnLaunch": true,
    "initialPosition": "",
}

Moving the window settings into their own object is tedious, but easy. Almost everything becomes a per-window setting.
Layering window settings is annoying. They'll work like
```
graph LR

uq[user: _quake]
uf[user: foo]
ub[user: base]
dq([defaults: _quake])
db[defaults: base]

uf  --> ub --> db
uq --> dq --> ub
```
- We make a "virtual" window settings blob if the user asks for a quake window.
- If the user does specify settings for the _quake window, then it'll still be applied on top of the "builtin" quake settings
If you don't use this at all, I don't think your settings will change at all¹
I don't have hot-reloading working
I don't have hot-renaming working
I don't have startupActions working
There are some other TODO!s I've left scattered.
I've added a new settings blob to per-window settings: dockWindow. These are for #11162 and #11174
- side: which side to "dock" to
- width & height: How big to make the window.
  - If >1, that value is treated as px
  - If <=1.0, that value is treated as a percent of the screen
- It also combines with centerOnLaunch, to center the window on that side
- It should warn if you set a value to <=0
- It should maybe obey initialPosition if centerOnLaunch isn't set
- It doesn't "dropdown" from the docked side
- It's a few pixels off from the right position. I think the ncSize.height is bigger than I'm expecting.
This altogether does nothing for #12594. It probably should!

an empty "windows":[] may be added. ↩︎

@zadjii-msft commented on GitHub (Sep 14, 2023): Alright, I'm calling it for this hackathon, but progress notes from the week: Latest branch was: `dev/migrie/fhl-fall-2023/11162-quake-III-arena` Sample JSON ```json { "name": "_quake", "defaultProfile": "haunter.gif", "dockWindow": { "side": "bottom", "width": 0.3, "height": 0.75 }, "centerOnLaunch": true, "initialPosition": "", } ``` * Moving the window settings into their own object is tedious, but easy. Almost everything becomes a per-window setting. * Layering window settings is _annoying_. They'll work like ```mermaid graph LR uq[user: _quake] uf[user: foo] ub[user: base] dq([defaults: _quake]) db[defaults: base] uf --> ub --> db uq --> dq --> ub ``` - We make a "virtual" window settings blob if the user asks for a quake window. - If the user does specify settings for the `_quake` window, then it'll still be applied on top of the "builtin" quake settings * If you don't use this at all, I don't think your settings will change at all[^1] * [ ] I don't have hot-reloading working * [ ] I don't have hot-renaming working * [ ] I don't have startupActions working * [ ] There are some other TODO!s I've left scattered. * I've added a new settings blob to per-window settings: `dockWindow`. These are for #11162 and #11174 - `side`: which side to "dock" to - `width` & `height`: How big to make the window. - If >1, that value is treated as px - If <=1.0, that value is treated as a percent of the screen - It also combines with `centerOnLaunch`, to center the window on that side - [ ] It should warn if you set a value to <=0 - [ ] It should maybe obey `initialPosition` if `centerOnLaunch` isn't set - [ ] It doesn't "dropdown" from the docked side - [ ] It's a few pixels off from the right position. I think the `ncSize.height` is bigger than I'm expecting. * [ ] This altogether does nothing for #12594. It probably should!  [^1]: an empty `"windows":[]` may be added.

claunia commented

@macleod-ee commented on GitHub (Nov 15, 2023):

Quick tip for everyone, you can set it to open in quake mode, and then set a keyboard shortcut to disable focus mode. I personally use win+ctrl+f for this. The tabs will remain in view for the entirety of the process lifetime.

@macleod-ee commented on GitHub (Nov 15, 2023): Quick tip for everyone, you can set it to open in quake mode, and then set a keyboard shortcut to disable focus mode. I personally use win+ctrl+f for this. The tabs will remain in view for the entirety of the process lifetime.

claunia commented

@Squidyy commented on GitHub (Mar 3, 2024):

Quick tip for everyone, you can set it to open in quake mode, and then set a keyboard shortcut to disable focus mode. I personally use win+ctrl+f for this. The tabs will remain in view for the entirety of the process lifetime.

Thank you this is very helpful

@Squidyy commented on GitHub (Mar 3, 2024): > Quick tip for everyone, you can set it to open in quake mode, and then set a keyboard shortcut to disable focus mode. I personally use win+ctrl+f for this. The tabs will remain in view for the entirety of the process lifetime. Thank you this is very helpful

claunia commented

@shookietea commented on GitHub (Mar 5, 2024):

Leaving my question here because it's related- I'm wanting quake mode functionality with a maximized window.

I've got a globalSummon action setup for a separate named _default window, with focus and maximized arguments. This mostly works (without the quake animation).

Is there a way to hide the taskbar icon when I've got this minimized, like the special _quake window does?

{
  "command": {
    "action": "globalSummon",
    "desktop": "toCurrent",
    "MaximizeAfterToggle": true,
    "dropdownDuration": 0,
    "monitor": "toMouse",
    "name": "_default",
    "toggleVisibility": true
  },
  "keys": "win+`"
  }

"startupActions": "wt --window _default -f -M \\; sp -V -s .666",

@shookietea commented on GitHub (Mar 5, 2024): Leaving my question here because it's related- I'm wanting quake mode functionality with a maximized window. I've got a `globalSummon` action setup for a separate named `_default` window, with focus and maximized arguments. This mostly works (without the quake animation). Is there a way to hide the taskbar icon when I've got this minimized, like the special `_quake` window does? ```json { "command": { "action": "globalSummon", "desktop": "toCurrent", "MaximizeAfterToggle": true, "dropdownDuration": 0, "monitor": "toMouse", "name": "_default", "toggleVisibility": true }, "keys": "win+`" } ``` `"startupActions": "wt --window _default -f -M \\; sp -V -s .666",`

claunia commented

@zadjii-msft commented on GitHub (Apr 1, 2024):

It's not really a "basic feature". It requires a pretty massive re-write of how our settings are stored. You can take a look at the all-up diff in https://github.com/microsoft/terminal/compare/main...dev/migrie/fhl-fall-2023/11162-quake-III-arena. There are piecemeal diffs listed in the OP as well. If you're passionate, you're more than free to take that over the finish line.

You're also free to just use "globalSummon" instead of "quakeMode". IMO that's got quite a bit more flexibility. I honestly love focus mode, but don't care at all for the dropdown, so I just use globalSummon.

@zadjii-msft commented on GitHub (Apr 1, 2024): It's not really a "basic feature". It requires a pretty massive re-write of how our settings are stored. You can take a look at the all-up diff in https://github.com/microsoft/terminal/compare/main...dev/migrie/fhl-fall-2023/11162-quake-III-arena. There are piecemeal diffs listed in the OP as well. If you're passionate, you're more than free to take that over the finish line. You're also free to just use "globalSummon" instead of "quakeMode". IMO that's got quite a bit more flexibility. I honestly love focus mode, but don't care at all for the dropdown, so I just use `globalSummon`.

claunia commented