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

Multiple Quake Windows can be opened #19569

New Issue
Open
opened 2026-01-31 06:47:31 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 06:47:31 +00:00
Owner
Copy Link

Originally created by @SubsTheTechnomancer on GitHub (Mar 23, 2023).

Windows Terminal version

1.16.10261.0

Windows build number

22000.1696

Other Software

No response

Steps to reproduce

  • Open a WT Instance and enter wt -w _quake
  • With the quake window open, enter the shortcut keys for opening/closing a quake window (In my case, Win + `)

Expected Behavior

The already open quake window should minimize as is normal while using the quake shortcut.

Actual Behavior

A different quake window opens either above the current quake window or on the currently active screen (if using multiple screens).

Originally created by @SubsTheTechnomancer on GitHub (Mar 23, 2023). ### Windows Terminal version 1.16.10261.0 ### Windows build number 22000.1696 ### Other Software _No response_ ### Steps to reproduce - Open a WT Instance and enter `wt -w _quake` - With the quake window open, enter the shortcut keys for opening/closing a quake window (In my case, Win + \`) ### Expected Behavior The already open quake window should minimize as is normal while using the quake shortcut. ### Actual Behavior A different quake window opens either above the current quake window or on the currently active screen (if using multiple screens).
claunia added the Issue-BugProduct-TerminalArea-UserInterfaceArea-Windowing labels 2026-01-31 06:47:32 +00:00
claunia commented 2026-01-31 06:47:33 +00:00
Author
Owner
Copy Link

@SubsTheTechnomancer commented on GitHub (Mar 23, 2023):

This might be related to #14957. I would have dismissed this as intended behaviour if not for the tip and tricks page provided (https://learn.microsoft.com/en-us/windows/terminal/tips-and-tricks). As an aside, I'm not sure what the intended behaviour is if, for example, you were to re-enter wt -w _quake a second time. Currently it creates a new tab in the existing quake window but I don't see any documentation related to this.

@SubsTheTechnomancer commented on GitHub (Mar 23, 2023): This might be related to #14957. I would have dismissed this as intended behaviour if not for the tip and tricks page provided (https://learn.microsoft.com/en-us/windows/terminal/tips-and-tricks). As an aside, I'm not sure what the intended behaviour is if, for example, you were to re-enter `wt -w _quake` a second time. Currently it creates a new tab in the existing quake window but I don't see any documentation related to this.
claunia commented 2026-01-31 06:47:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 23, 2023):

Do you have both Terminal Preview and Terminal stable installed? Are you possibly running one Terminal instance elevated (as admin)/?

I'd be sure that this isn't #14957 - that's only just been checked in and is only available on internal 1.18 builds.

Doing wt -w _quake a second time perhaps isn't documented the best. That implicitly turns into wt -w _quake new-tab, which essentially turns into "open a new tab in the window named _quake".

@zadjii-msft commented on GitHub (Mar 23, 2023): Do you have both Terminal Preview and Terminal stable installed? Are you possibly running one Terminal instance elevated (as admin)/? I'd be sure that this isn't #14957 - that's only just been checked in and is only available on internal 1.18 builds. Doing `wt -w _quake` a second time perhaps isn't documented the best. That implicitly turns into `wt -w _quake new-tab`, which essentially turns into "open a new tab in the window named `_quake`".
claunia commented 2026-01-31 06:47:33 +00:00
Author
Owner
Copy Link

@SubsTheTechnomancer commented on GitHub (Mar 27, 2023):

Are you possibly running one Terminal instance elevated (as admin)/?

By default, my terminal instances are elevated, yes. Is that the reason for this behaviour?

@SubsTheTechnomancer commented on GitHub (Mar 27, 2023): > Are you possibly running one Terminal instance elevated (as admin)/? By default, my terminal instances are elevated, yes. Is that the reason for this behaviour?
claunia commented 2026-01-31 06:47:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 27, 2023):

Probably - though, there should only be one _quake window for the elevated instances, and one single _quake window for the unelevated ones.

Can you check something for me quick/? In each of the open _quake windows, can you open the Command Palette (ctrl+shift+p), then perform the "Toggle focus mode" action? That should make the titlebar (and tabs) of the _quake window visible. Do both windows have a sheild icon in the top left, like so:

image

If they both do, that's very peculiar, and I might want to take a look at your settings.json file next.

If they DON'T both have one, then this is totally by design.

@zadjii-msft commented on GitHub (Mar 27, 2023): Probably - though, there should only be one `_quake` window for the elevated instances, and one single `_quake` window for the unelevated ones. Can you check something for me quick/? In each of the open `_quake` windows, can you open the Command Palette (<kbd>ctrl+shift+p</kbd>), then perform the "Toggle focus mode" action? That should make the titlebar (and tabs) of the `_quake` window visible. Do both windows have a sheild icon in the top left, like so: ![image](https://user-images.githubusercontent.com/18356694/227932448-bdd10d53-b02e-4a29-b97f-08f4516d80f8.png) If they both do, that's very peculiar, and I might want to take a look at your [settings.json file](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-file) next. If they DON'T both have one, then this is totally by design.
claunia commented 2026-01-31 06:47:34 +00:00
Author
Owner
Copy Link

@SubsTheTechnomancer commented on GitHub (Mar 27, 2023):

I did this, and yeah, the one instantiated by the command is not an elevated terminal, so it does seem to be by design.
Unfortunately, then, I'm not sure how I would open an elevated quake window with the command, unless this is already documented.

@SubsTheTechnomancer commented on GitHub (Mar 27, 2023): I did this, and yeah, the one instantiated by the command is not an elevated terminal, so it does seem to be by design. Unfortunately, then, I'm not sure how I would open an elevated quake window with the command, unless this is already documented.
claunia commented 2026-01-31 06:47:34 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 29, 2023):

Alright I think this is crazy. But here's my thoughts on what's going on

  • you launch WT unelevated. This takes the global hotkeys.
  • We evaluate the settings, and relaunch as an elevated instance. (presumably due to profiles.defaults.elevated=true).
  • You launch wt -w _quake, which creates an elevated quake window.
  • You press the hotkey - this somehow runs in the unelevated instance.

The issue that for some reason, the unelevated terminal instance is still running. Only one process can hold on to the global hotkeys.

The issue is that there's that first unelevated instance that's still running. That would be something to investigate.

@zadjii-msft commented on GitHub (Mar 29, 2023): Alright I think this is crazy. But here's my thoughts on what's going on * you launch WT unelevated. This takes the global hotkeys. * We evaluate the settings, and relaunch as an elevated instance. (presumably due to `profiles.defaults.elevated=true`). * You launch `wt -w _quake`, which creates an elevated quake window. * You press the hotkey - this somehow runs in the _unelevated instance_. The issue that for some reason, the unelevated terminal instance is still running. Only one process can hold on to the global hotkeys. The issue is that there's that first unelevated instance that's still running. That would be something to investigate.
claunia commented 2026-01-31 06:47:34 +00:00
Author
Owner
Copy Link

@SubsTheTechnomancer commented on GitHub (Mar 30, 2023):

I believe you may have swapped which instance in elevated and which is not, but I think the problem is still the same, except that it is the elevated instance that is getting priority over the global hotkeys.

@SubsTheTechnomancer commented on GitHub (Mar 30, 2023): I believe you may have swapped which instance in elevated and which is not, but I think the problem is still the same, except that it is the elevated instance that is getting priority over the global hotkeys.
claunia commented 2026-01-31 06:47:35 +00:00
Author
Owner
Copy Link

@cypherfunc commented on GitHub (Oct 2, 2023):

related/repeat of #11478?

@cypherfunc commented on GitHub (Oct 2, 2023): related/repeat of #11478?
claunia commented 2026-01-31 06:47:35 +00:00
Author
Owner
Copy Link

@cypherfunc commented on GitHub (Oct 2, 2023):

For reference, none of my quake tabs are elevated

@cypherfunc commented on GitHub (Oct 2, 2023): For reference, none of my quake tabs are elevated
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 Area-UserInterface Area-Windowing Issue-Bug Product-Terminal
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#19569
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?