Open ratiomark opened 2 months ago
This may be related. Only some keybindings work with the cursor chat panel text input is focused. I've pasted some keybinding logs below. First, you can see an example of the alt-o
command working when focused on the editor. Beginning at 00:42:29.858
, you can see the alt-o
command failing when the chat text input is focused. This is true for other bindings like cmd+o
as well.
Interestingly, other custom keybindings (such as alt-t
) work with the chat text input focused.
2024-10-24 00:42:18.573 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-10-24 00:42:18.575 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-10-24 00:42:18.575 [info] [KeybindingService]: / Received keydown event - modifiers: [alt], code: AltRight, keyCode: 18, key: Alt
2024-10-24 00:42:18.576 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltRight, keyCode: 6 ('Alt')
2024-10-24 00:42:18.576 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-10-24 00:42:18.580 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-10-24 00:42:18.581 [info] [KeybindingService]: | Resolving alt+O
2024-10-24 00:42:18.581 [info] [KeybindingService]: \ From 2 keybinding entries, matched terminal.focus, when: no when condition, source: user.
2024-10-24 00:42:18.581 [info] [KeybindingService]: / Received keydown event - modifiers: [alt], code: KeyO, keyCode: 79, key: Unidentified
2024-10-24 00:42:18.581 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: KeyO, keyCode: 45 ('O')
2024-10-24 00:42:18.581 [info] [KeybindingService]: | Resolving alt+O
2024-10-24 00:42:18.581 [info] [KeybindingService]: \ From 2 keybinding entries, matched terminal.focus, when: no when condition, source: user.
2024-10-24 00:42:18.581 [info] [KeybindingService]: + Invoking command terminal.focus.
2024-10-24 00:42:18.674 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-10-24 00:42:18.674 [info] [KeybindingService]: | Resolving alt+O
2024-10-24 00:42:18.675 [info] [KeybindingService]: \ From 2 keybinding entries, matched terminal.focus, when: no when condition, source: user.
2024-10-24 00:42:18.733 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-10-24 00:42:18.736 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-10-24 00:42:18.736 [info] [KeybindingService]: + Ignoring single modifier alt due to it being pressed together with other keys.
2024-10-24 00:42:29.858 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-10-24 00:42:29.858 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-10-24 00:42:29.858 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-10-24 00:42:29.864 [info] [KeybindingService]: | Resolving alt+O
2024-10-24 00:42:29.864 [info] [KeybindingService]: \ From 2 keybinding entries, matched terminal.focus, when: no when condition, source: user.
2024-10-24 00:42:30.041 [info] [KeybindingService]: + Ignoring single modifier alt due to it being pressed together with other keys.
System Specifications:
Please note that while I’m using Windows 11, the system displays it as "Windows_NT x64 10.0.22631" due to the way the operating system versions are reported internally.
Hello,
I’m experiencing several issues related to custom keybindings and the general functionality of hotkeys. Below are the details:
Custom Keybinding for Closing Prompt Bar:
Ctrl + B
as the keybinding to close the prompt bar using the following configuration inkeybindings.json
:Ctrl + B
does not have any effect. The window still only closes usingEsc
.Hotkey Functionality Inside Prompt Bar and AI Chat:
Ctrl + Shift + P
does not bring up the Command Palette.Custom Hotkey for Chat Dropdown:
aichat.showchatdropdown
command fromCtrl + Alt + L
toCtrl + Alt + M
. The UI reflects this change, as seen in the attached screenshot. However, pressingCtrl + Alt + M
does nothing, while the originalCtrl + Alt + L
still works.I would appreciate it if you could look into these issues.
Please add the bug label to this issue if applicable