We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From @mvolkmann on August 3, 2018 16:1
Issue Type: Bug
The Vim keybindings were working fine. Then I opening User Settings. From that point all all Vim keybindings stopped working.
VS Code version: Code - Insiders 1.26.0-insider (4fa62b246c4305b4ca00507551f77c58135ce928, 2018-08-03T12:25:19.888Z) OS version: Darwin x64 16.7.0
Copied from original issue: microsoft/vscode#55768
The text was updated successfully, but these errors were encountered:
From @vscodebot[bot] on August 3, 2018 16:2
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
Sorry, something went wrong.
@mvolkmann, what do you see when you turn on verbose logging: https://github.com/VSCodeVim/Vim#debugging-remappings
Closing as haven't heard anything back. Feel free to re-open if there is additional information you can provide.
rebornix
No branches or pull requests
From @mvolkmann on August 3, 2018 16:1
Issue Type: Bug
The Vim keybindings were working fine. Then I opening User Settings. From that point all all Vim keybindings stopped working.
VS Code version: Code - Insiders 1.26.0-insider (4fa62b246c4305b4ca00507551f77c58135ce928, 2018-08-03T12:25:19.888Z)
OS version: Darwin x64 16.7.0
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Extensions (26)
Copied from original issue: microsoft/vscode#55768
The text was updated successfully, but these errors were encountered: