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

Elevated profile doesn't open Quake terminal #16410

New Issue
Open
opened 2026-01-31 05:07:30 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 05:07:30 +00:00
Owner
Copy Link

Originally created by @elsaco on GitHub (Jan 15, 2022).

Windows Terminal version

main 7061c54

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

  • add new profile and set "elevate": true
  • open new profile
  • close previous terminal window
  • open Quake terminal

Expected Behavior

  • quake mode terminal

Actual Behavior

  • no quake mode terminal window:

wt_elevate_quake_mode_not_working

Originally created by @elsaco on GitHub (Jan 15, 2022). ### Windows Terminal version main 7061c54 ### Windows build number 10.0.19044.0 ### Other Software _No response_ ### Steps to reproduce - add new profile and set `"elevate": true` - open new profile - close previous terminal window - open Quake terminal ### Expected Behavior - quake mode terminal ### Actual Behavior - no quake mode terminal window: ![wt_elevate_quake_mode_not_working](https://user-images.githubusercontent.com/3933920/149632404-4cd1c007-80ee-4ef0-839d-b15b8ea7d920.png)
claunia added the Issue-TaskProduct-TerminalArea-Remoting labels 2026-01-31 05:07:30 +00:00
claunia commented 2026-01-31 05:07:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 18, 2022):

This is likely what happened

  1. You started the terminal, and it took the win+` hotkey
  2. You started an elevated terminal. It trued to take the win+` hotkey, but found it was already bound, so it failed.
  3. You closed the unelevated Terminal. Nothing here tells the elevated Terminal to take over the keyboard shortcuts
  4. You press win+`, but no one has that key bound.

I suspect this isn't the only time we're going to hear this on this release. Not sure what a good solution is. Maybe an elevated flag to globalSummon, as a bool?, that can filter to {any window, unelevated only, elevated only}?

This would be the release to handle this, that's for sure.

@zadjii-msft commented on GitHub (Jan 18, 2022): This is likely what happened 1. You started the terminal, and it took the <kbd>win+`</kbd> hotkey 2. You started an _elevated_ terminal. It trued to take the <kbd>win+`</kbd> hotkey, but found it was already bound, so it failed. 3. You closed the unelevated Terminal. Nothing here tells the elevated Terminal to take over the keyboard shortcuts 4. You press <kbd>win+`</kbd>, but no one has that key bound. I suspect this isn't the only time we're going to hear this on this release. Not sure what a good solution is. Maybe an `elevated` flag to `globalSummon`, as a `bool?`, that can filter to {any window, unelevated only, elevated only}? This would be the release to handle this, that's for sure.
claunia commented 2026-01-31 05:07:40 +00:00
Author
Owner
Copy Link

@User1785604260 commented on GitHub (Mar 2, 2023):

Coming here from #9996. I'd like to have a way to enforce that the new headless terminal from #14944 is the only thing registering the Win+` quakeMode hotkey. This is so that I can ensure quakeMode windows are always unelevated (my preference) by launching the headless terminal as unelevated.

As it currently stands, there's a race as too which terminal starts first and captures the hotkey. If I open an elevated terminal immediately on login, I can find myself locked into elevated-only quakeMode terminals.

@User1785604260 commented on GitHub (Mar 2, 2023): Coming here from #9996. I'd like to have a way to enforce that the new headless terminal from #14944 is the only thing registering the Win+\` quakeMode hotkey. This is so that I can ensure quakeMode windows are always unelevated (my preference) by launching the headless terminal as unelevated. As it currently stands, there's a race as too which terminal starts first and captures the hotkey. If I open an elevated terminal immediately on login, I can find myself locked into elevated-only quakeMode terminals.
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-Remoting Issue-Task 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#16410
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?