VS Developer Prompts do not attach to window, conflict with allowHeadless #20042

Closed
opened 2026-01-31 07:01:38 +00:00 by claunia · 3 comments
Owner

Originally created by @JVimes on GitHub (Jun 6, 2023).

Windows Terminal version

1.18.1462.0

Windows build number

10.0.19045.0

Other Software

Visual Studio 17.7.0 Preview 1.0

Steps to reproduce

  1. Select "Windows Terminal" for "Default terminal application" under Startup.
  2. Set "windowingBehavior": "useAnyExisting" and open a terminal.
  3. From Start, run "Developer PowerShell for VS 2022" or "Developer Command Prompt for VS 2022" from Visual Studio.

Expected Behavior

The developer prompt is new tab in the existing terminal window.

Actual Behavior

The developer prompt opens in a second instance of Windows Terminal. This creates another problem with alwaysShowNotificationIcon and the new compatibility.allowHeadless, where the extra notification area icon can't be closed without killing WindowsTerminal.exe.

2023-06-06_11h22_45

Originally created by @JVimes on GitHub (Jun 6, 2023). ### Windows Terminal version 1.18.1462.0 ### Windows build number 10.0.19045.0 ### Other Software Visual Studio 17.7.0 Preview 1.0 ### Steps to reproduce 1. Select "Windows Terminal" for "Default terminal application" under Startup. 1. Set `"windowingBehavior": "useAnyExisting"` and open a terminal. 1. From Start, run "Developer PowerShell for VS 2022" or "Developer Command Prompt for VS 2022" from Visual Studio. ### Expected Behavior The developer prompt is new tab in the existing terminal window. ### Actual Behavior The developer prompt opens in a second instance of Windows Terminal. This creates another problem with `alwaysShowNotificationIcon` and the new `compatibility.allowHeadless`, where the extra notification area icon can't be closed without killing WindowsTerminal.exe. ![2023-06-06_11h22_45](https://github.com/microsoft/terminal/assets/6148201/1f8f0f21-1407-4463-bc79-73907f2fd143)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:01:38 +00:00
Author
Owner

@JVimes commented on GitHub (Jun 6, 2023):

CC @zadjii-msft 🙂

@JVimes commented on GitHub (Jun 6, 2023): CC @zadjii-msft 🙂
Author
Owner

@zadjii-msft commented on GitHub (Jul 10, 2023):

This sounds exactly like the same thing as /dup #15509. Thanks!

@zadjii-msft commented on GitHub (Jul 10, 2023): This sounds exactly like the same thing as /dup #15509. Thanks!
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Jul 10, 2023):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Jul 10, 2023): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20042