Unable to disable/remap Escape key closing CommentThreadWidget #231674
Labels
bug
Issue identified by VS Code Team member as probable bug
comments
Comments Provider/Widget/Panel issues
insiders-released
Patch has been released in VS Code Insiders
verified
Verification succeeded
Milestone
Type: Bug
This recently merged PR unfortunately partially broke the VSCodeVim comment editor integration (issue) as it added a un-remappable key binding for Escape to close the comment panel. Vim maps Escape to leave whichever mode is currently active, which is no longer possible since the code introduced by the PR gets triggered instead.
Is there a way to re-implement the newly added Escape keybinding using the regular vscode keybinding configuration? This would allow the vim extension to remap it so that it doesn't collide with the vim specific Escape binding.
Steps to reproduce:
Expected outcome: Comment thread widget stays visible, with vim returning to normal mode
Actual outcome: Comment thread widget is closed
VS Code version: Code 1.94.2 (384ff73, 2024-10-09T16:08:44.566Z)
OS version: Darwin arm64 23.6.0
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Extensions (4)
The text was updated successfully, but these errors were encountered: