-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
magit keybindings for interactive rebase #2174
Comments
They are remapped via the macro |
@syl20bnr Can you try it? "K" is not mapped for me, and there's no emacs state to go into ("C-z" does nothing). It seems like a special "magit select" buffer. I don't have time right now to dig into what's going on, but it doesn't seem to be working. I'm on develop with emacs25. |
I got in through |
This is because I overload it when passing additonal bindings :-( Weird that it does nothing for you though. We should put the additional bindings on |
Some more information. I didn't notice these messages before, although they may not be relevant to this exactly. These are recorded right after
|
This is not related. I'm aware of these warnings, I have to find good Le jeudi 2 juillet 2015, Justin Burkett notifications@github.com a écrit :
-syl20bnr- |
I don't mind too much where the keybindings go (although I wish "k" for kill could be remapped to "d"). I was more interested in doing something with the comment section, so that it's not completely wrong. Unfortunately it seems to be hardcoded: https://github.com/magit/magit/blob/fb3e25dd776d83d5cb459a183bc128c652375d9e/lisp/git-rebase.el#L341-L367 |
You know like me that there is no such thing has "hardcoded" in elisp ;-) If d is free then I see no problem to tweak the map to include it. We can Le jeudi 2 juillet 2015, Justin Burkett notifications@github.com a écrit :
-syl20bnr- |
Yes, of course :-) Any ideas on |
I guess evil has a dedicated variable for the temporary state, we can support it in the wrappers. |
I'm not sure a temporary state is what I'm thinking about. I can't explain why, but sometimes the vim-like keybindings are more natural to me but other times the emacs-like ones are. Could we maybe have a variable that prevents certain maps from being evilified? I appreciate the effort you put into making a consistent interface, but I still find myself getting lost and confused (maybe that's my problem and not yours). |
Never mind. That's probably going to make it more complicated. There's just so many different states now that it's hard to keep track of what's going on sometimes. |
@justbur you can remove the magit modes from |
Oh, I didn't know about those variables. Thanks. Sorry, I wasn't saying something had changed. I was just reporting that the message in the rebase buffer was wrong about the keybindings and that I was having trouble figuring out the right ones. Thanks for your help |
Resolved with #3578 |
Is there some way to change the key binding hints at the bottom since they're wrong? They say "k" for delete commit or something like that for example. But "k" is now move one line up. Also, I couldn't figure out where "k" got remapped to.
The text was updated successfully, but these errors were encountered: