viper.el is hardcoded to disable viper
in compilation-mode
. How can I fix this without modifying the original file?
Asked
Active
Viewed 133 times
0

Natan Yellin
- 6,063
- 5
- 38
- 57
2 Answers
2
If you really want to do this, you should be able to customize the variable viper-emacs-state-mode-list
and remove compilation-mode
.

Luke Girvin
- 13,221
- 9
- 64
- 84
-
Yes, I really want to. I can't stand getting trapped in a compilation window where all my shortcuts stop working. I can add my own mappings. – Natan Yellin Sep 08 '11 at 15:58
-
@Natan Yellin - fair enough - so, did you try to customize the variable? It seems to work for me. – Luke Girvin Sep 08 '11 at 16:14
-
Yes, this did the trick: `(setq viper-emacs-state-mode-list ())` – Natan Yellin Sep 13 '11 at 15:29
0
Have you tried running "M-x viper-mode"? That's what I do when I end up in a buffer in which it has been disabled, or at least not enabled.

Howard West
- 381
- 3
- 6