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

After trying out Quake mode, running wt -w 0 sp -s 0.4 pwsh from any non-quake mode WT terminal always opens a new terminal window #18459

Open
daxian-dbw opened this issue Jan 24, 2025 · 5 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements

Comments

@daxian-dbw
Copy link
Member

Windows Terminal version

1.22.3232.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

  1. Run wt --window _quake to try out the Quake mode
  2. Close all Quake mode window, then open a new regular WT window, run wt -w 0 sp -s 0.4 pwsh within it

Expected Behavior

The command wt -w 0 sp -s 0.4 pwsh should split the current window and run PowerShell in the new pane

Actual Behavior

After trying out the Quake mode, running wt -w 0 sp -s 0.4 pwsh from WT (regular window, non-Quake mode) will always start a new window and split it over there, instead of splitting the current window.

@daxian-dbw daxian-dbw 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 24, 2025
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@zadjii-msft
Copy link
Member

Yea, this is definitely the same thing as /dup #13466. -w 0 should work for _quake, we just forgot to make that work.

Copy link
Contributor

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 microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jan 24, 2025
@zadjii-msft zadjii-msft reopened this Jan 24, 2025
Copy link
Contributor

This issue has been marked as duplicate and has not had any activity for 1 day. It will be closed for housekeeping purposes.

@zadjii-msft
Copy link
Member

oh pish posh bot

@zadjii-msft zadjii-msft reopened this Jan 26, 2025
@zadjii-msft zadjii-msft removed the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jan 26, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Tag-Fix Doesn't match tag requirements label Jan 26, 2025
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-Tag-Fix Doesn't match tag requirements
Projects
None yet
Development

No branches or pull requests

2 participants