-
Notifications
You must be signed in to change notification settings - Fork 133
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
Please provide a keybinding for whichkey.undoKey for when people set up VSpaceCode on intro screen #329
Comments
The back button on the top menu bar would work, but I agree it is not keyboard friendly. Do you any suggestion on which key we should bind to? |
I'd go with u or b or similar. |
So this issue is about going back in the menu. b and u can conflict with other keys, right? What about backspace? |
That's perfect! Back to go back! |
That's correct.
One can bind this backspace with https://vspacecode.github.io/docs/whichkey/extra#use-non-character-keys. Then a user effective can't use this key. In spacemacs, one can undo key via The UI part is the difficult part, which is why this command For now, the workaround is bind that key manually using
|
What do you mean by the UI part is the hard part? Getting the menu update and go to previous screen on a 'ctrl +h' like hitting the GUI back arrow? |
When I say UI, I meant to emulate the ![]() When a press
There are however some idiosyncratic behaviors to this
Option 1: Keep it simple
Option 2: emulate
|
I like option 1. Keep it simple and ctrl u works well. I'm not tied to any specific implementation if that is a factor or not. |
Problem
Please provide a keybinding for whichkey.undoKey for when people set up VSpaceCode on intro screen
Solution
Update keybinding file on the first setup for whichkey.undoKey.
Alternatives
Checking documentation looking for a back key
Checking tooling using ? to look for back or undo
Digging into VspaceCode website looking for keybinding
This will make it easier to look around without redo hit esc, ... or other various implementations.
or have to do ? search for command.
Both options work but don't provide an easy way to poke around for newer users of the ecosystem the tool is providing (spacemacs for example).
Additional context
If a user doesn't know what to search for it makes it easier to poke around the various key binds in VS Code and then go back.
Thank you for the awesome tool also! Makes it very easy to use overall keybindings and figure out needed keyboard-driven commands outside of VIM within VS Code. Also you all are killing it on the documentation front as well.
The text was updated successfully, but these errors were encountered: