Open DanKaplanSES opened 11 months ago
Workaround: if you right-click on the keyboard shortcut setting and reset it, the row will go back to a "System" source and then ctrl + f will go back to behaving like normal.
Hi @DanKaplanSES ,
This's an interesting find, thank you for the issue!
More details on why this is happening:
We first create a new keybinding and then remove the old keybinding. However, we then modify the keybinding we introduced, which if matches the unbound keybinding will be unbound. See:
https://github.com/microsoft/vscode/assets/16353531/87f62856-efb7-485b-8caf-78f819a5ca26
Type: Bug
actions.find
's "When" expression toeditorFocus || editorIsOpen || terminal.active
actions.find
's back to the way it was:editorFocus || editorIsOpen
Expected: workbench.action.terminal.focusFind executes, opening a search box in your terminal Actual: The keyboard shortcut has no effect
I turned on keyboard shortcut troubleshooting and it printed this:
VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:51:52.184Z) OS version: Windows_NT x64 10.0.19045 Modes:
System Info
|Item|Value| |---|---| |CPUs|AMD Ryzen 7 2700X Eight-Core Processor (16 x 3700)| |GPU Status|2d_canvas: enabledcanvas_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
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|undefined| |Memory (System)|31.93GB (23.43GB free)| |Process Argv|--disable-extensions --remote=wsl+Ubuntu| |Screen Reader|no| |VM|0%|