-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
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
Vim navigate on quickfix #3556
Comments
In my experience, this extension be broken if you are using global search. |
Quick Fix navigation works with C-p and C-n but not with the popular C-j C-k custom keybindings // Place your key bindings in this file to override the defaults
[
{
"key": "ctrl+j",
"command": "workbench.action.quickOpenSelectNext",
"when": "inQuickOpen"
},
{
"key": "ctrl+k",
"command": "workbench.action.quickOpenSelectPrevious",
"when": "inQuickOpen"
},
{
"key": "ctrl+j",
"command": "selectNextSuggestion",
"when": "editorTextFocus && suggestWidgetVisible"
},
{
"key": "ctrl+k",
"command": "selectPrevSuggestion",
"when": "editorTextFocus && suggestWidgetVisible"
},
{
"key": "ctrl+h",
"command": "list.collapse",
"when": "listFocus && !inputFocus"
},
{
"key": "ctrl+l",
"command": "list.expand",
"when": "listFocus && !inputFocus"
},
{
"key": "ctrl+j",
"command": "list.focusDown",
"when": "listFocus && !inputFocus"
},
{
"key": "ctrl+k",
"command": "list.focusUp",
"when": "listFocus && !inputFocus"
}
] I think we can custom bind it with Reference: https://code.visualstudio.com/docs/getstarted/keybindings |
@sluongng Quick Fix navigation with C-p and C-n is only work in Mac OS not window. |
This is not possible because they use a native popup. I created a extension as a workaround: It uses the quick open picker to display codeactions. |
Thank @PascalSenn I really want to have that extension. |
A good workaround that I found. Give a shot guys > microsoft/vscode#55111 (comment) |
Describe the solution you'd like
Open quick fix and use vim to navigate on the list. Now I can only use arrow key to navigate
The text was updated successfully, but these errors were encountered: