Unable to remove specific keybindings

[SogoCZE]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

I noticed that you cannot remove specific keybindings. If you remove a keybinding from the custom keybinding config, it will fall back to the default one. The problem I have is that in my Czech keyboard layout, I type { with alt-b and } with alt-n, and there are default keybindings for these combinations, so I cannot type { in Zed right now.

To solve this, I would suggest either:

1. Allowing to pass an empty string, false, or null as a keybinding command, so that these keybinds wouldn't block the default OS behavior.
2. Don't fall back to default keybindings.

Environment

Zed 0.66.0 – /Applications/Zed.app
macOS 13.0
architecture arm64

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue

No response

[tom2strobl]

On mac/german using alt-v prints this character: √ which I personally like to use in quick notes to mark as something completed. Zed currently has

"alt-v": ["editor::MovePageUp", { "center_cursor": true }],

which I'd like to deactivate.

[probablykasper]

Alt+<character> should probably not be used for any shortcuts by default. Alt+V is like Shift+V, it's already used for typing characters.

[DanielBreiner]

Any update on this? It's been the top-ranked defect issue for quite some time now and makes the software unusable for people who use certain keyboard layouts.

[DanielBreiner]

After half a year, Zed is still unusable for a large number of european developers :( . Could we at least get a response from the devs that they are aware of this issue and some estimate on when this might get fixed -- or at least some statement about its priority?

[SogoCZE]

@JosephTLyons

[JosephTLyons]

Hey all, I brought this up with the team today in our meeting. We will put emphasis on fixing it - sorry for dropping the ball for so long here. I'll update the issue when I know where the fix might land.