-
Notifications
You must be signed in to change notification settings - Fork 16
Inconsistent keybindings after adding forge support #60
Comments
How can we disable these "new and improved" forge keybindings? For anyone landing here from spacemacs you can use the following to keep
|
Excluding Forge is not a solution though. The default magit bindings are - |
If you're Spacemacs/evil user and just like me frustrated about that change:
Honestly, I'd rather sacrifice submodules popup ( |
@yqrashawn Just load forge automatically when you load |
I reverted the forge changes |
I think you should calm down and show some respect. If not, don’t use this package and bind the keys yourself or pay someone to do it. Being disrespectful and rude to a maintainer who spends her/his free time developing software is just plain wrong. You may voice your concerns but damn it, show some respect. |
Thank you @justbur, much appreciated. Would it be possible to move evil-magit's submodule binding to make room for the forge binding? Maybe this could be an opt-in flag for now so that it does not disrupt anyone's muscle memory (though I'd imagine submodule stuff is lower impact than push/pull). |
@aaronjensen I reopened #54 to discuss further. |
Forge won't load until user call
forge-dispatch
when usinguse-package
to install forge. So the keybindings areF
for pulling andp
for push.The problem is
forge
by keypressesforge
toF
forforge-dispatch
,P
for pulling, which is inconsistentThe text was updated successfully, but these errors were encountered: