Running wt -w 0 -p <profile> while existing Terminal window is open causes the window to be minimized #14062

Closed
opened 2026-01-31 03:59:48 +00:00 by claunia · 3 comments
Owner

Originally created by @djsavvy on GitHub (May 31, 2021).

Windows Terminal version (or Windows build number)

1.9.1445.0

Other Software

No response

Steps to reproduce

This behavior started with Preview build 1.9.1445.0 in my experience.

If I run wt -w 0 -p <profile name> while the existing WT window is focused, the new tab opens with the correct profile, but the entire window gets minimized for some reason.

At first I though this was just an issue with AutoHotKey, but I was able to reproduce it by running the command via Win+R. Make sure that the existing WT window is focused, though, since focusing a different window and then running the command caused the new profile tab to open without the existing window being minimized.

Expected Behavior

The tab opening without the window being minimized, in all cases.

Actual Behavior

The tab opened, but the window got minimized.

Originally created by @djsavvy on GitHub (May 31, 2021). ### Windows Terminal version (or Windows build number) 1.9.1445.0 ### Other Software _No response_ ### Steps to reproduce This behavior started with Preview build 1.9.1445.0 in my experience. If I run `wt -w 0 -p <profile name>` __while the existing WT window is focused__, the new tab opens with the correct profile, but the entire window gets minimized for some reason. At first I though this was just an issue with AutoHotKey, but I was able to reproduce it by running the command via Win+R. Make sure that the existing WT window is focused, though, since focusing a different window and then running the command caused the new profile tab to open without the existing window being minimized. ### Expected Behavior The tab opening without the window being minimized, in all cases. ### Actual Behavior The tab opened, but the window got minimized.
Author
Owner

@zadjii-msft commented on GitHub (May 31, 2021):

Oh my god I know exactly what I did.

When we summon the window because a commandline has been dispatched to it, we use a default-constructed window summon behavior. And the default behavior is to toggle visibility. It shouldn't toggle, it should always just summon. Good catch!

@zadjii-msft commented on GitHub (May 31, 2021): Oh my god I know exactly what I did. When we summon the window because a commandline has been dispatched to it, we use a default-constructed window summon behavior. And the default behavior is to toggle visibility. It shouldn't toggle, it should always just summon. Good catch!
Author
Owner

@ghost commented on GitHub (Jul 14, 2021):

:tada:This issue was addressed in #10396, which has now been successfully released as Windows Terminal v1.9.1942.0.🎉

Handy links:

@ghost commented on GitHub (Jul 14, 2021): :tada:This issue was addressed in #10396, which has now been successfully released as `Windows Terminal v1.9.1942.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.9.1942.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Author
Owner

@ghost commented on GitHub (Jul 14, 2021):

:tada:This issue was addressed in #10396, which has now been successfully released as Windows Terminal Preview v1.10.1933.0.🎉

Handy links:

@ghost commented on GitHub (Jul 14, 2021): :tada:This issue was addressed in #10396, which has now been successfully released as `Windows Terminal Preview v1.10.1933.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.10.1933.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14062