starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal interferes with global hotkeys assigned to another app #6497

New Issue
Closed
opened 2026-01-31 00:40:21 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 00:40:21 +00:00
Owner
Copy Link

Originally created by @davidjade on GitHub (Feb 17, 2020).

I have an Win32 tray app installed (3RVX) that allows me to configure the Windows Key + Scroll Wheel (middle mouse button) to alter the system volume. This is a global hotkey combination. When I open a Windows Terminal and it has the focus, this global hotkey no longer works. When I switch to any other app, then it works again.

Environment

Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0
Terminal Version: 0.9.433.0

Any other software?
https://www.3rvx.com/

Steps to reproduce

  1. Install 3RVX and config to use Windows + Scroll Wheel to change the system volume.
  2. Install Windows Terminal preview from Store
  3. Open Terminal and keep focused, then try Windows + Scroll Wheel hotkey to change system volume - this does not work. If you switch to any other app then the hotkey combination works.

Expected behavior

Should not interfere with another app's global hotkey configuration that uses the Windows+Scroll wheel.

Actual behavior

Prevents another app's Windows+Scroll hotkey from working

Originally created by @davidjade on GitHub (Feb 17, 2020). I have an Win32 tray app installed (3RVX) that allows me to configure the Windows Key + Scroll Wheel (middle mouse button) to alter the system volume. This is a global hotkey combination. When I open a Windows Terminal and it has the focus, this global hotkey no longer works. When I switch to any other app, then it works again. # Environment Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Terminal Version: 0.9.433.0 Any other software? https://www.3rvx.com/ # Steps to reproduce 1. Install 3RVX and config to use Windows + Scroll Wheel to change the system volume. 2. Install Windows Terminal preview from Store 3. Open Terminal and keep focused, then try Windows + Scroll Wheel hotkey to change system volume - this does not work. If you switch to any other app then the hotkey combination works. # Expected behavior Should not interfere with another app's global hotkey configuration that uses the Windows+Scroll wheel. # Actual behavior Prevents another app's Windows+Scroll hotkey from working
claunia commented 2026-01-31 00:40:22 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 21, 2020):

I'm concerned about this one, actually. I've not run into any other applications that Terminal consumes the key bindings for...
It seems like there's a >0 chance that 3RVX is doing something untowards to get at the keyboard queue.

Do the hotkeys added by 3RVX work when you're looking at Calc, or Magnifier (in Windows 10.0.19041)?

@DHowett-MSFT commented on GitHub (Feb 21, 2020): I'm concerned about this one, actually. I've not run into any other applications that Terminal consumes the key bindings for... It seems like there's a >0 chance that 3RVX is doing something untowards to get at the keyboard queue. Do the hotkeys added by 3RVX work when you're looking at Calc, or Magnifier (in Windows 10.0.19041)?
claunia commented 2026-01-31 00:40:22 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 21, 2020):

(magnifier changed in 19041 to an architecture that's like Terminal's, weirdly enough, so it can help us repro issues like this)

@DHowett-MSFT commented on GitHub (Feb 21, 2020): (magnifier changed in 19041 to an architecture that's like Terminal's, weirdly enough, so it can help us repro issues like this)
claunia commented 2026-01-31 00:40:22 +00:00
Author
Owner
Copy Link

@davidjade commented on GitHub (Feb 21, 2020):

3RVX defined hotkeys seem to work fine with Calc, magnifier, etc... It's just the new Terminal app and it seems just the hotkeys that use the key + mouse scroll are affected. 3RVX source appears to be here, btw : https://github.com/malensek/3RVX

@davidjade commented on GitHub (Feb 21, 2020): 3RVX defined hotkeys seem to work fine with Calc, magnifier, etc... It's just the new Terminal app and it seems just the hotkeys that use the key + mouse scroll are affected. 3RVX source appears to be here, btw : https://github.com/malensek/3RVX
claunia commented 2026-01-31 00:40:22 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 21, 2020):

So, weird enough, I can't get this to happen. I bound Win+WheelUp to Volume Up and it works in Terminal and everywhere else. 3RVX Beta 10.

@DHowett-MSFT commented on GitHub (Feb 21, 2020): So, weird enough, I can't get this to happen. I bound Win+WheelUp to Volume Up and it works in Terminal and everywhere else. 3RVX Beta 10.
claunia commented 2026-01-31 00:40:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 21, 2020):

Triaged into backlog as P2: If we can get a repro, this will be important to fix. Could be an external issue, but we're not yet sure.

@DHowett-MSFT commented on GitHub (Feb 21, 2020): Triaged into backlog as P2: If we can get a repro, this will be important to fix. Could be an external issue, but we're not yet sure.
claunia commented 2026-01-31 00:40:23 +00:00
Author
Owner
Copy Link

@jstaro commented on GitHub (Oct 7, 2021):

I'm concerned about this one, actually. I've not run into any other applications that Terminal consumes the key bindings for...

I also have a similar, hopefully related, problem which might be a clue.
I currently have Win+Ctrl+Space bound to show PowerToys Run, and pressing that key combination works in all programs I'm using, except Windows Terminal. Pressing that key combination when Windows Terminal has focus transforms that global hotkey into just Win+Space, because it will trigger the Language Bar quick switch.

So, either Windows Terminal is somehow swallowing the Ctrl key, when used as part of a hotkey combination that includes the Win key, or it could be an issue with how PowerToys Run processes key events.

I haven't yet tried binding that same hotkey in another program to rule out PowerToys Run being naughty.

@jstaro commented on GitHub (Oct 7, 2021): > I'm concerned about this one, actually. I've not run into any other applications that Terminal consumes the key bindings for... I also have a similar, hopefully related, problem which might be a clue. I currently have Win+Ctrl+Space bound to show PowerToys Run, and pressing that key combination works in all programs I'm using, except Windows Terminal. Pressing that key combination when Windows Terminal has focus transforms that global hotkey into just Win+Space, because it will trigger the Language Bar quick switch. So, either Windows Terminal is somehow swallowing the Ctrl key, when used as part of a hotkey combination that includes the Win key, or it could be an issue with how PowerToys Run processes key events. I haven't yet tried binding that same hotkey in another program to rule out PowerToys Run being naughty.
claunia commented 2026-01-31 00:40:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 26, 2022):

@davidjade You still seeing this on a fresh build of 3RVX/? They may have just fixed this on their side in the last few years.

@jstaro I can't seem to repro that on a 0.57 build of PowerToys, I suspect they may have fixed that on their side

@zadjii-msft commented on GitHub (Jul 26, 2022): @davidjade You still seeing this on a fresh build of 3RVX/? They may have just fixed this on their side in the last few years. @jstaro I can't seem to repro that on a 0.57 build of PowerToys, I suspect they may have fixed that on their side
claunia commented 2026-01-31 00:40:23 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 30, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jul 30, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Input Issue-Bug Needs-Author-Feedback Needs-Repro No-Recent-Activity Priority-2 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#6497
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?