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

Canary can't verify the window first time Launch #22744

New Issue
Closed
opened 2026-01-31 08:22:12 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:22:12 +00:00
Owner
Copy Link

Originally created by @CN-CODEGOD on GitHub (Jan 6, 2025).

Windows Terminal version

1.23.10011.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

i am looking at document for wt -w command and want to write a script to send multiple commands to a window

I want to launch command on the specific window with
& "f:\terminal-1.23.10011.0\wt.exe" -w foo -p "Python" ping baidu.com

When Launching as default profile ,and run command to the first Launching window,will not verify the windows
F:\terminal-1.23.10011.0\wt.exe -w 0 -p "Powershell"
& "f:\terminal-1.23.10011.0\wt.exe" -w 0 -p "Python" ping baidu.com
try different profile and different commandLine
F:\terminal-1.23.10011.0\wt.exe -w foo -p "Powershell"
& "f:\terminal-1.23.10011.0\wt.exe" -w foo -p "Python" ping baidu.com
still fail

Expected Behavior

The command should run in the Launching window

Actual Behavior

command run in the new window

note

i am using two version of wt
canary :1.23.10011.0
wt:1.22.3232.0
for what i know the two version work fine together ,i also try to Launch command to the 1.22.3232.0 version and still fail

Originally created by @CN-CODEGOD on GitHub (Jan 6, 2025). ### Windows Terminal version 1.23.10011.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce i am looking at [document](https://learn.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows) for wt -w command and want to write a script to send multiple commands to a window I want to launch command on the specific window with & "f:\terminal-1.23.10011.0\wt.exe" -w foo -p "Python" ping baidu.com When Launching as default profile ,and run command to the first Launching window,will not verify the windows F:\terminal-1.23.10011.0\wt.exe -w 0 -p "Powershell" & "f:\terminal-1.23.10011.0\wt.exe" -w 0 -p "Python" ping baidu.com try different profile and different commandLine F:\terminal-1.23.10011.0\wt.exe -w foo -p "Powershell" & "f:\terminal-1.23.10011.0\wt.exe" -w foo -p "Python" ping baidu.com still fail ### Expected Behavior The command should run in the Launching window ### Actual Behavior command run in the new window ### note i am using two version of wt canary :1.23.10011.0 wt:1.22.3232.0 for what i know the two version work fine together ,i also try to Launch command to the 1.22.3232.0 version and still fail
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:22:12 +00:00
claunia commented 2026-01-31 08:22:13 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 7, 2025):

You've closed the issue. Have you solved the problem? What was the solution?

@DHowett commented on GitHub (Jan 7, 2025): You've closed the issue. Have you solved the problem? What was the solution?
claunia commented 2026-01-31 08:22:13 +00:00
Author
Owner
Copy Link

@CN-CODEGOD commented on GitHub (Jan 8, 2025):

I didn't fix the issue,but rather that i realize the problem occurred when using wt command as profile in windows terminal,so i open it manually so it verify the window correctly.
I am still looking forward a way of starting up the quake mode in start up and set it as default profile

@CN-CODEGOD commented on GitHub (Jan 8, 2025): I didn't fix the issue,but rather that i realize the problem occurred when using wt command as profile in windows terminal,so i open it manually so it verify the window correctly. I am still looking forward a way of starting up the quake mode in start up and set it as default profile
claunia commented 2026-01-31 08:22:14 +00:00
Author
Owner
Copy Link

@CN-CODEGOD commented on GitHub (Jan 8, 2025):

I didn't fix the issue,but rather that i realize the problem occurred when using wt command as profile in windows terminal,so i open it manually so it verify the window correctly.
I am still looking forward a way of setting the quake mode as default profile

@CN-CODEGOD commented on GitHub (Jan 8, 2025): > I didn't fix the issue,but rather that i realize the problem occurred when using wt command as profile in windows terminal,so i open it manually so it verify the window correctly. > I am still looking forward a way of setting the quake mode as default profile
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#22744
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?