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

"startupActions": with quake mode are not behaving correctly #17182

New Issue
Closed
opened 2026-01-31 05:34:35 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 05:34:35 +00:00
Owner
Copy Link

Originally created by @mullcom on GitHub (Apr 8, 2022).

Windows Terminal version

1.13.10733.0

Windows build number

10.0.19044.1586]

Other Software

No response

Steps to reproduce

Run command in a sinel terminal
wt -w _quake ;sp -H;sp;sp

Then test add this now to settings json file
"startupActions": "wt -w _quake sp -H;sp;sp",

Expected Behavior

All sp i add in startupActions wt command should release on quake mode window.

Actual Behavior

i have try to get several sp in but only manage get one sp in quake mode the rest adds to startup terminal.

Originally created by @mullcom on GitHub (Apr 8, 2022). ### Windows Terminal version 1.13.10733.0 ### Windows build number 10.0.19044.1586] ### Other Software _No response_ ### Steps to reproduce Run command in a sinel terminal wt -w _quake ;sp -H;sp;sp Then test add this now to settings json file "startupActions": "wt -w _quake sp -H;sp;sp", ### Expected Behavior All sp i add in startupActions wt command should release on quake mode window. ### Actual Behavior i have try to get several sp in but only manage get one sp in quake mode the rest adds to startup terminal.
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 05:34:35 +00:00
claunia commented 2026-01-31 05:34:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 8, 2022):

I don't think wt -w is supported in startupActions at all... Hmm.

@zadjii-msft commented on GitHub (Apr 8, 2022): I don't think `wt -w` is supported in `startupActions` _at all_... Hmm.
claunia commented 2026-01-31 05:34:37 +00:00
Author
Owner
Copy Link

@mullcom commented on GitHub (Apr 8, 2022):

it working with two SP so but failing when i add more. yast test it for your self and you find out.

zadjii-msft commented on Jul 26, 2021
At the moment, not really.

You could do something like wt -w _quake -p {your profile name} - that'll launch the Terminal into quake mode with the profile of your choice.
You could always rebind quakeMode to a generic globalSummon action. That'd let you just summon any Terminal window, not just the quake one.
Otherwise, you could wait for https://github.com/microsoft/terminal/issues/9992 to be able to change the defaultProfile of the _quake window separately from the normal default

@mullcom commented on GitHub (Apr 8, 2022): it working with two SP so but failing when i add more. yast test it for your self and you find out. [zadjii-msft](https://github.com/zadjii-msft) commented [on Jul 26, 2021](https://github.com/microsoft/terminal/issues/10796#issuecomment-886814545) At the moment, not really. You could do something like wt -w _quake -p {your profile name} - that'll launch the Terminal into quake mode with the profile of your choice. You could always rebind quakeMode to a generic [globalSummon](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/actions#global-commands) action. That'd let you just summon any Terminal window, not just the quake one. Otherwise, you could wait for https://github.com/microsoft/terminal/issues/9992 to be able to change the defaultProfile of the _quake window separately from the normal default
claunia commented 2026-01-31 05:34:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 1, 2022):

Okay I see what's going on here.

When you put wt -w _quake sp ; sp ; sp into startup actions, here's what happens:

  • the terminal parses this into three subcommands: [wt -w _quake sp, sp, sp]
  • The first one doesn't parse as an action. wt isnt a subcommand, so we treat it as a commandline. We run a tab with the commandline wt -w _quake sp.
    • THIS CREATES A NEW WINDOW, the quake window, with a commandline of sp
    • The quake window defaults to creating a tab. Then it processes the sp, splitting the pane.
  • The original terminal window then parses a sp, and creates a new split for this sp.
  • The original terminal window then parses a sp, and creates a new split for this sp.

So, you end up with two terminal windows, a _quake window and a normal one, each with two panes.

Putting -w in the startupActions is definitely not recommended. What I was talking about above was running wt -w _quake sp ; sp ; sp from like, the run dialog, or a shortcut, or another Terminal window. Putting the above into startupActions will cause the _quake window to create a new split each and every launch, which would be weird.

@zadjii-msft commented on GitHub (Aug 1, 2022): Okay I see what's going on here. When you put `wt -w _quake sp ; sp ; sp` into startup actions, here's what happens: * the terminal parses this into three subcommands: [`wt -w _quake sp`, `sp`, `sp`] * The first one doesn't parse as an action. `wt` isnt a subcommand, so we treat it as a commandline. We run a tab with the commandline `wt -w _quake sp`. * THIS CREATES A NEW WINDOW, the quake window, with a commandline of `sp` * The quake window defaults to creating a tab. Then it processes the `sp`, splitting the pane. * The original terminal window then parses a `sp`, and creates a new split for this `sp`. * The original terminal window then parses a `sp`, and creates a new split for this `sp`. So, you end up with two terminal windows, a `_quake` window and a normal one, each with two panes. Putting `-w` in the `startupActions` is definitely _not_ recommended. What I was talking about above was running `wt -w _quake sp ; sp ; sp` from like, the run dialog, or a shortcut, or another Terminal window. Putting the above into `startupActions` will cause the \_quake window to create a new split each and every launch, which would be weird.
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-Question Needs-Tag-Fix Needs-Triage 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#17182
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?