Subsequent `wt.exe /min` to an existing window restores a minimized window

[YO4]

Windows Terminal version

1.22.2702.0

Windows build number

10.0.19045.4894

Other Software

No response

Steps to reproduce

new console creating wt.exe respects /min
start /min wt.exe -w exam -> new wt, single tab, minimized
start /min wt.exe -w exam sp -> new wt, single tab, minimized, two panes

Expected Behavior

start /min wt.exe -w exam && ^
(echo "sleep 1.0" && ping -n 2 localhost) > NUL && ^
start /min wt.exe -w exam sp

-> minimized wt, single tab, two panes

Actual Behavior

start /min wt.exe -w exam && ^
(echo "sleep 1.0" && ping -n 2 localhost) > NUL && ^
start /min wt.exe -w exam sp

-> visible wt, single tab, two panes

[zadjii-msft]

Hmm. Seems that when the second commandline is tossed at the original window, we summon it, always.

I bet there's a way to not summon it if the commandline had a /min on it.

This is where we're getting the visibility of the request:

terminal/src/cascadia/WindowsTerminal/WindowEmperor.cpp

Lines 93 to 95 in 3a06826

	const Remoting::CommandlineArgs eventArgs{ args, cwd, gsl::narrow_cast<uint32_t>(nCmdShow), std::move(env) };
	const auto isolatedMode{ _app.Logic().IsolatedMode() };
	const auto result = _manager.ProposeCommandline(eventArgs, isolatedMode);

Good catch here, thanks!

---

oneliner

start /min wt.exe -w exam && (echo "sleep 1.0" && ping -n 2 localhost) > NUL && start /min wt.exe -w exam sp