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

--window flag does not work as anticipated #15140

New Issue
Closed
opened 2026-01-31 04:29:39 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 04:29:39 +00:00
Owner
Copy Link

Originally created by @acederberg on GitHub (Sep 8, 2021).

Windows Terminal version (or Windows build number)

1.11.2421.0

Other Software

Windows 10 Pro 10.0.19043 Build 19043
Note that the version number provided for windows terminal is for the preview.

Steps to reproduce

Make sure all instances of windows terminal are closed first. Run the following script

wt --window 0
wt --window 1

by

powershell.exe -file

or just enter the script line by line into the terminal. I also tried running it from powershell ISE and got the same result.

Expected Behavior

Expected wt --window n to specify the nth window or spawn it. When no instances of wt are open, then the above script should open the zeroth and first windows.

Actual Behavior

Spawned both instances of wt into a single window. However when I run

wt --window 0
wt --window 2

I get the anticipated output, two separate windows both in the default profile.

Originally created by @acederberg on GitHub (Sep 8, 2021). ### Windows Terminal version (or Windows build number) 1.11.2421.0 ### Other Software Windows 10 Pro 10.0.19043 Build 19043 Note that the version number provided for windows terminal is for the preview. ### Steps to reproduce Make sure all instances of windows terminal are closed first. Run the following script wt --window 0 wt --window 1 by powershell.exe -file <name of script> or just enter the script line by line into the terminal. I also tried running it from powershell ISE and got the same result. ### Expected Behavior Expected `wt --window n` to specify the nth window or spawn it. When no instances of wt are open, then the above script should open the zeroth and first windows. ### Actual Behavior Spawned both instances of wt into a single window. However when I run wt --window 0 wt --window 2 I get the anticipated output, two separate windows both in the default profile.
claunia commented 2026-01-31 04:29:40 +00:00
Author
Owner
Copy Link

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

Window IDs start at 1. 0 is a special reserved ID for "this window I'm currently running in". So when you do wt --window 0 ; wt --window 1, what's happening is the first commandline finds no windows, and assigns itself the ID 1. Then the second command runs, and runs itself in the first window.

The docs sorta mention this?

@zadjii-msft commented on GitHub (Sep 8, 2021): Window IDs start at 1. `0` is a special reserved ID for "this window I'm currently running in". So when you do `wt --window 0 ; wt --window 1`, what's happening is the first commandline finds _no_ windows, and assigns itself the ID 1. Then the second command runs, and runs itself in the first window. The docs [sorta mention this](https://docs.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows#target-a-specific-window)?
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 Area-Remoting Issue-Question Needs-Tag-Fix Needs-Triage Product-Terminal Resolution-Answered
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#15140
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?