aboutsummaryrefslogtreecommitdiffstats
path: root/emacs/.emacs.d/init.el
diff options
context:
space:
mode:
authorGravatar Tom Willemse2016-07-25 22:14:22 +0200
committerGravatar Tom Willemse2016-07-25 22:14:22 +0200
commit425c0318851fbd88485185f1be091af7c56c794d (patch)
tree94b16f5af1e78fb4da59b0e1afd33e19e7ec6c8b /emacs/.emacs.d/init.el
parentaacc23547f595da7c19202c405259e5e78856d34 (diff)
downloadnew-dotfiles-425c0318851fbd88485185f1be091af7c56c794d.tar.gz
new-dotfiles-425c0318851fbd88485185f1be091af7c56c794d.zip
Add some whitespace settings
Diffstat (limited to 'emacs/.emacs.d/init.el')
-rw-r--r--emacs/.emacs.d/init.el15
1 files changed, 15 insertions, 0 deletions
diff --git a/emacs/.emacs.d/init.el b/emacs/.emacs.d/init.el
index 42854f0..5db6481 100644
--- a/emacs/.emacs.d/init.el
+++ b/emacs/.emacs.d/init.el
@@ -167,6 +167,21 @@ This is currently the data directory under the
;; whereabouts I am, so they just take up space.
(scroll-bar-mode -1)
+;;;; Whitespace:
+;; I hate it when trailing whitespace is left around a file. I've been
+;; using this for years, and apart from having some trouble working
+;; with people who don't pay attention to it, it has worked
+;; flawlessly.
+(ensure-library destroy-trailing-whitespace
+ :path "vendor-lisp/destroy-trailing-whitespace")
+(require 'destroy-trailing-whitespace)
+(global-destroy-trailing-whitespace-mode)
+
+;; Having a final newline at the end of the file is always a good
+;; idea. Some programs just don't work without it and others produce
+;; some strange results. Github diffs are an example.
+(setq require-final-newline t)
+
;;;; Minor modes:
;;;;; Paredit: