You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, first of all thank you for this great project :)
I've been trying some things with dance, and I've come to the conclusion that a lot of the shortcuts are messed up for my keyboard. For example, search (/) is mapped to the (#) key for me. And it seems to be the same for some other shortcuts, cause stuff isn't working like it's supposed to. I have a german quwertz keyboard. I've read some issues, in which you described the choice to default to vs code keymapping instead of doing it like the vim plugin. I agree with the decision, but I think that for this to work properly one would need some kind of keymap setup process. Something like a dialog, which asks the user to press the shortcut for the appropriate symbol for the command. Like "Press / to setup the shortcut for the search command".
The text was updated successfully, but these errors were encountered:
This is actually the main idea behind the next planned release (0.6). Basically, I'd like to disable all default keybindings and add a dialog that can easily generate many keybindings with layout-specific defaults. I don't have time to tend to this at all these days, but if you have suggestions or a "formal" list of mappings (ie something that I could easily transform into a JSON mapping with a short script) from Qwerty to Qwertz, I'll take it for later!
Hey, first of all thank you for this great project :)
I've been trying some things with dance, and I've come to the conclusion that a lot of the shortcuts are messed up for my keyboard. For example, search (/) is mapped to the (#) key for me. And it seems to be the same for some other shortcuts, cause stuff isn't working like it's supposed to. I have a german quwertz keyboard. I've read some issues, in which you described the choice to default to vs code keymapping instead of doing it like the vim plugin. I agree with the decision, but I think that for this to work properly one would need some kind of keymap setup process. Something like a dialog, which asks the user to press the shortcut for the appropriate symbol for the command. Like "Press / to setup the shortcut for the search command".
The text was updated successfully, but these errors were encountered: