-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
custom keybind is lower precedence than vim keybind #21358
Comments
@penzboti on Linux, |
oh. I thought from your previous |
I looked into this a bit today, and I can reproduce the problem with ctrl-k; I am not sure yet why it is broken. You also seem to have issues with é being spelled as eacute - I'd like to fix this when we do the next pass on Linux shortcuts. |
Related problem with key precedence: e.g. I was setting up more helix-like tab throughs.: Defaults {
"context": "Editor && showing_completions",
"bindings": {
"enter": "editor::ConfirmCompletion",
"tab": "editor::ComposeCompletion"
}
}, Custom -- higher precedence, will override [
{
"context": "Editor && showing_completions",
"bindings": {
"tab": null,
"shift-tab": null
}
}, Custom -- low precedence, won't work [
{
"context": "Editor && showing_completions",
"bindings": {
"tab": "menu::SelectNext",
"shift-tab": "editor::ContextMenuPrev"
}
}, (Adjusting the location of the overrides in the keymap.json also had no effect. Precedence viewed with the KeybindDebugger) Edit
![]() |
Check for existing issues
Describe the bug / provide steps to reproduce it
I can't because multiple keybinds work normally while overwriting the default vim keybind, but one doesn't.
Environment
Zed: v0.161.2 (Zed)
OS: Linux Wayland nixos 25.05
Memory: 3.5 GiB
Architecture: x86_64
GPU: Intel(R) Graphics (ADL-N) || Intel open-source Mesa driver || Mesa 24.2.6
If applicable, add mockups / screenshots to help explain present your vision of the feature
a keybind that works:




and a keybind that doesn't:
(the vim mode was insert, but my screenshot tool updated the context)
If applicable, attach your Zed.log file to this issue.
Zed.log
The text was updated successfully, but these errors were encountered: