Ex-vimmer also. As Dan pointed out in the comment of OP, binding to C-c is too devastating in emacs. What I do is instead binding to C-c C-c so I can hit C-c like a crazy person to get back to normal. (Just like hitting C-s 10 times is the proper way to save MS Word documents, I do this a lot: C-c C-c C-c ... C-c C-g C-g ... C-g to make sure I'm in normal ...
The evil keybindings seem not to work for me in every major mode as either.
What might help is to add the evil-collection package.
But what I did to really make sure that my keybinding for switching windows is:
(define-key term-raw-map (kbd "C-<left>") 'evil-window-left)
(define-key term-raw-map (kbd "C-&...
I'm not sure why it is interrupted by evil mode.
It's interrupted by evil mode to switch into the "emacs" state, a mode where evil falls back into your regular Emacs keybindings:
C-z runs the command evil-emacs-state (found in evil-motion-state-map), which is an interactive compiled Lisp
function in ‘evil-states.el’...
event-apply-meta-modifier is only to be used in translation keymaps. You
(define-key key-translation-map "'" 'event-apply-meta-modifier)
(define-key key-translation-map ";" 'event-apply-control-modifier)
This will also make it possible to use these keys in the middle of a key
sequence. If you want the keys to only work in ...
This answer is based on this evil-mode mailinglist post
Short answer: This is expected behavior.
In python-mode (and elpy), when you start typing, hitting TAB will not do anything, presumably preventing you from accidental TAB inserts which will trigger errors in Python interpreter. The other way arround TAB results in a "Tab" (e.g. 4 ...
Evil faithfully emulates Vim, including the part of C-i and C-o being bound in normal state to commands going through the jump list. C-i happens to be equivalent to TAB for reasons (hello terminals), so another thing you'll observe is it being bound in insert state to something else, like an indentation command. If you dislike that behavior, you've got two ...