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
<C-j>
<C-k>
Describe the bug
If you go to the command edit box that opens at the top of VS Code, ctrl+j/k don't work to navigate options. They work in autocompletion box.
The command edit box is opened when you go to symbol (ctrl+shift+o), look for file (ctrl+p) and run command (ctrl+shift+p).
To Reproduce Steps to reproduce the behavior:
By default ctrl+j toggles a pane. I disabled this mapping.
Expected behavior I expect the highlighted symbol (or file or command) to change. When I press Enter I expect the highlighted symbol to be selected.
Environment (please complete the following information):
vim
0.17.0
Windows_NT x64 10.0.17763
1.30.0
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Is there any way to make this work?
Sorry, something went wrong.
This will be a great feature! Before that, there is a replacement solution with keybinding. #4305 (comment)
No branches or pull requests
Describe the bug
If you go to the command edit box that opens at the top of VS Code, ctrl+j/k don't work to navigate options. They work in autocompletion box.
The command edit box is opened when you go to symbol (ctrl+shift+o), look for file (ctrl+p) and run command (ctrl+shift+p).
To Reproduce
Steps to reproduce the behavior:
By default ctrl+j toggles a pane. I disabled this mapping.
Expected behavior
I expect the highlighted symbol (or file or command) to change. When I press Enter I expect the highlighted symbol to be selected.
Environment (please complete the following information):
vim
0.17.0
Windows_NT x64 10.0.17763
1.30.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: