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

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 #22795

New Issue
Open
opened 2026-01-31 08:23:45 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:23:45 +00:00
Owner
Copy Link

Originally created by @daxian-dbw on GitHub (Jan 24, 2025).

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.

Originally created by @daxian-dbw on GitHub (Jan 24, 2025). ### 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.
claunia added the Issue-BugNeeds-Tag-Fix labels 2026-01-31 08:23:45 +00:00
claunia commented 2026-01-31 08:23:46 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Jan 24, 2025):

We've found some similar issues:

  • #13466 , similarity score: 84%
  • #15037 , similarity score: 82%

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.

@similar-issues-ai[bot] commented on GitHub (Jan 24, 2025): We've found some similar issues: - #13466 , similarity score: 84% - #15037 , similarity score: 82% 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.
claunia commented 2026-01-31 08:23:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 24, 2025):

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

@zadjii-msft commented on GitHub (Jan 24, 2025): Yea, this is definitely the same thing as /dup #13466. `-w 0` _should_ work for `_quake`, we just forgot to make that work.
claunia commented 2026-01-31 08:23:47 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jan 24, 2025):

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[bot] commented on GitHub (Jan 24, 2025): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
claunia commented 2026-01-31 08:23:47 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jan 26, 2025):

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

@microsoft-github-policy-service[bot] commented on GitHub (Jan 26, 2025): This issue has been marked as duplicate and has not had any activity for **1 day**. It will be closed for housekeeping purposes. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
claunia commented 2026-01-31 08:23:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 26, 2025):

oh pish posh bot

@zadjii-msft commented on GitHub (Jan 26, 2025): oh pish posh bot
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-Tag-Fix
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#22795
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?