Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
CN-CODEGOD opened this issue Jan 6, 2025 · 3 comments
Closed

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

CN-CODEGOD opened this issue Jan 6, 2025 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@CN-CODEGOD
Copy link

CN-CODEGOD commented 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

@CN-CODEGOD CN-CODEGOD added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jan 6, 2025
@DHowett
Copy link
Member

DHowett commented Jan 7, 2025

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

@CN-CODEGOD
Copy link
Author

CN-CODEGOD commented 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
Copy link
Author

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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants