starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Wt window being visible when spawning wt -w 0 -p profile_name #19093

New Issue
Closed
opened 2026-01-31 06:33:32 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 06:33:32 +00:00
Owner
Copy Link

Originally created by @brupelo on GitHub (Dec 18, 2022).

Windows Terminal version

1.15.3465.0

Windows build number

Microsoft Windows [Version 10.0.19045.2364]

Other Software

No response

Steps to reproduce

When you run the command wt -w 0 -p profile_name you can see each time a new wt process is spawned a new terminal subwindow will appear very fast and then will be attached/docked to the master window.

Is this behaviour intended? If not, is there any existing way to prevent this behaviour and make it more clean without the user being aware how this temporary subwindow is being created "behind the curtains"?

References:

Expected Behavior

Similar clean/non-intrusive behaviour of spawning wt -w 0 -p profile_name than pressing the + button

image

Actual Behavior

Here's an example of what I mean:

https://user-images.githubusercontent.com/18058492/208300229-4903e6e5-7aa8-40ca-b69f-1ba18c81b4bc.mp4

Originally created by @brupelo on GitHub (Dec 18, 2022). ### Windows Terminal version 1.15.3465.0 ### Windows build number Microsoft Windows [Version 10.0.19045.2364] ### Other Software _No response_ ### Steps to reproduce When you run the command `wt -w 0 -p profile_name` you can see each time a new wt process is spawned a new terminal subwindow will appear very fast and then will be attached/docked to the master window. Is this behaviour intended? If not, is there any existing way to prevent this behaviour and make it more clean without the user being aware how this temporary subwindow is being created "behind the curtains"? References: - [https://learn.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows#target-a-specific-window](https://learn.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows#target-a-specific-window) - [https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/ns-processthreadsapi-startupinfoa#syntax](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/ns-processthreadsapi-startupinfoa#syntax) ### Expected Behavior Similar clean/non-intrusive behaviour of spawning `wt -w 0 -p profile_name` than pressing the + button ![image](https://user-images.githubusercontent.com/18058492/208300368-731681cb-c0c6-4634-a2af-e4720c3095c6.png) ### Actual Behavior Here's an example of what I mean: https://user-images.githubusercontent.com/18058492/208300229-4903e6e5-7aa8-40ca-b69f-1ba18c81b4bc.mp4
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 06:33:32 +00:00
claunia commented 2026-01-31 06:33:33 +00:00
Author
Owner
Copy Link

@brupelo commented on GitHub (Dec 18, 2022):

False positive, the behaviour was on my end caused by using an old sublime package https://github.com/codexns/newterm. When spawning wt with python's subprocess.run or spawning the process directly from a normal shell everything works fine

@brupelo commented on GitHub (Dec 18, 2022): False positive, the behaviour was on my end caused by using an old sublime package [https://github.com/codexns/newterm](https://github.com/codexns/newterm). When spawning `wt` with python's subprocess.run or spawning the process directly from a normal shell everything works fine
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19093
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?