Closed Nowaaru closed 4 months ago
This is to be expected, the function used for setting keybinds does not handle null
cases. I can add a handler for that, but I am not sure if I want to support unsetting binds rather than overriding.
what's the problem with unsetting? I can see it being useful, with how easy it is to end up with keybinds that conflict with defaults
@NotAShelf @horriblename It is expected to handle null cases as we support null mappings for every other module. The issue here is that it doesn't use genMaps
like other modules which filters them out. We don't use vim.maps.*
because mappings are conditionally activated on LSP attach.
I made a PR to add the check.
⚠️ Please verify that this bug has NOT been reported before.
Description
Mappings specified in the documentation error out when setting the options to
null
. Assuming this occurs for allmkBinding
calls.👟 Reproduction steps
Set a mapping to
null
.👀 Expected behavior
The mapping should disable.
😓 Actual Behavior
The mapping errors.
💻 Metadata
"x86_64-linux"
- host os:Linux 6.6.29, NixOS, 24.05 (Uakari), 24.05.20240502.63c3a29
- multi-user?:yes
- sandbox:yes
- version:nix-env (Nix) 2.21.2
- nixpkgs:/nix/store/p69bcs7ma6ijj8v9xsrg3nq3nn8ryn95-source
📝 Relevant log output