Browse Source

[Fix #663] Make guru-mode warn by default

custom
Bozhidar Batsov 11 years ago
parent
commit
fda768992e
  1. 12
      README.md
  2. 3
      modules/prelude-programming.el

12
README.md

@ -587,19 +587,17 @@ If you get some http connection error related to the MELPA repo
just do a manual `M-x package-refresh-contents` and restart Emacs
afterwards.
### No arrow navigation in editor buffers
### Warnings on arrow navigation in editor buffers
This is not a bug - it's a feature! I firmly believe that the one true
way to use Emacs is by using it the way it was intended to be used (as
far as navigation is concerned at least). That's why I've disabled all
movement commands with arrows (and keys like page up, page down,
etc) - to prevent you from being tempted to use them.
far as navigation is concerned at least).
If you'd like to be able to use the arrow keys (but still be reminded of
the alternatives) put this in your personal config:
If you'd like to be take this a step further and disable the arrow key navigation
completely put this in your personal config:
```lisp
(setq guru-warn-only t)
(setq guru-warn-only nil)
```
To disable `guru-mode` completely add the following snippet to your

3
modules/prelude-programming.el

@ -117,6 +117,9 @@ This functions should be added to the hooks of major modes for programming."
'(((lambda (&rest _ignored)
(prelude-smart-open-line-above)) "RET")))
;; enlist a more liberal guru
(setq guru-warn-only t)
(defun prelude-prog-mode-defaults ()
"Default coding hook, useful with any programming language."
(when (and (executable-find ispell-program-name)

Loading…
Cancel
Save