Permalink
Browse files

Didn't realize that require-final-newline sometimes sneaks in there

  • Loading branch information...
1 parent cc27131 commit 9f02acee385bf8af11442401811504bf44d43140 @glasserc committed Jun 28, 2012
Showing with 6 additions and 1 deletion.
  1. +3 −1 README.rst
  2. +3 −0 lisp/ethan-wspace.el
View
4 README.rst
@@ -122,7 +122,9 @@ like the following::
You should also remove any customizations you have made to turn on
either ``show-trailing-whitespace`` or ``require-final-newline``; we
-handle those for you.
+handle those for you. (But note that ``require-final-newline`` is
+turned on by some modes based on the value of
+``mode-require-final-newline``.)
When you open files (N.B. but not non-file buffers), bad whitespace
will be highlit and clean whitespace will be maintained. You can
View
3 lisp/ethan-wspace.el
@@ -65,6 +65,9 @@
;; FIXME: buffer-local-ize ethan-wspace-errors
;;
;; FIXME: coding conventions suggest adding a ethan-wspace-unload-hook to unhook
+;;
+;; FIXME: warn if no-nl highlighting is turned on and
+;; require-final-newline is on. Maybe even turn it off?
;; We store the whitespace types here.
;; Currently each whitespace type is represented as an association list

0 comments on commit 9f02ace

Please sign in to comment.