Skip to content
This repository has been archived by the owner on Oct 25, 2022. It is now read-only.

Initial state of magit-popup #47

Open
A6GibKm opened this issue Jun 11, 2018 · 2 comments
Open

Initial state of magit-popup #47

A6GibKm opened this issue Jun 11, 2018 · 2 comments

Comments

@A6GibKm
Copy link

A6GibKm commented Jun 11, 2018

I have to put

(general-define-key
 :states 'emacs
 :keymaps 'magit-popup-mode-map
 "j"	 'forward-button
 "k"	 'backward-button)

in my config since magit-popup uses emacs-state by default (contrary to magit-status), can this be changed to normal state? In the past I tried to manually change it to normal state using evil-initial-state resulting in breakage of magit-popup.

@BooAA
Copy link

BooAA commented Oct 23, 2018

Having same viewpoint here, I think using normal-state for all magit related mode will be better. Many people will set evil-emacs-state-modes , evil-insert-state-modes and evil-motion-state-modes to nil, which is conflict with some modes defined in evil-magit-untouched-modes. I think making all modes start in normal-state can fix this problem.

@justbur
Copy link
Member

justbur commented Oct 25, 2018

Magit popups don't use regular keymaps to get key bindings. If I remember right, they intercept keypresses in such a way that you have to actually be inserting the character corresponding to the shortcut into the buffer. In terms of evil, that means you should be in emacs state or insert state in those buffers. I don't think insert makes much sense.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants