Improve structure, add more explanations

1 files changed, 92 insertions, 54 deletions

diff --git a/.emacs.d/init.org b/.emacs.d/init.org
index 30d1703..80007b3 100644
--- a/.emacs.d/init.org
+++ b/.emacs.d/init.org
@@ -52,48 +52,82 @@
     ;; -*- lexical-binding: t -*-
   #+END_SRC
 
-* Cleanup basic UI
+* Remove some UI elements
 
-  The tool-bar, menu-bar and scroll-bar aren't particularly
-  keyboard-friendly and just take up space if you don't use them.
-  Anything in the tool-bar or menu-bar can be accessed just as easily
-  with {{{key(M-x)}}}. The scroll-bar is almost just as informative as
-  the current line number and buffer position information.
+  Some elements are only really useful if you use the mouse. Which I
+  don't, not if I can help it. Only when browsing the web or using the
+  odd graphical application do I touch the mouse, and even then as
+  little as I can.
 
-  #+BEGIN_SRC emacs-lisp
-    (menu-bar-mode -1)
-    (tool-bar-mode -1)
-    (scroll-bar-mode -1)
-  #+END_SRC
+** Menu bar
 
-* Stop blinking!
+   The menu bar is one of the UI elements which work best with mouses.
+   Sure you can change your toolkit's key bindings to allow you to
+   more easily navigate, but {{{key(M-x)}}} or {{{key(M-`)}}}[fn:1]
+   are easier if you don't use the mouse. Long story short: It has got
+   to go.
 
-  Blinking cursors are a distraction.
+   #+BEGIN_SRC emacs-lisp
+     (menu-bar-mode -1)
+   #+END_SRC
 
-  #+BEGIN_SRC emacs-lisp
-    (blink-cursor-mode -1)
-  #+END_SRC
+** Tool bar
 
-* Buffer position
+   The toolbar is another such thing, and it takes up quite a bit more
+   space too. Icons can look pretty cool, but in the end if you're not
+   going to click them they don't really server much of a purpose.
+   Again: It has got to go.
 
-  As I'm currently using svg-mode-line-themes[fn:1] for my ~mode-line~ I
-  don't need to show these. Also I didn't really use them much, I
-  don't often need to know what line I'm on.
+   #+BEGIN_SRC emacs-lisp
+     (tool-bar-mode -1)
+   #+END_SRC
 
-  #+BEGIN_SRC emacs-lisp
-    (column-number-mode -1)
-    (line-number-mode -1)
-  #+END_SRC
+** Scroll bar
 
-* Don't show tooltips
+   The scroll-bar is almost just as informative as the current line
+   number and buffer position information shown in the (my) mode line.
+   As I don't usually need to know where I am, other than the current
+   line number occasionally, and I don't use the mouse, the scroll bar
+   doesn't add anything and only takes up space. Once more: It has got
+   to go.
 
-  Tooltips are another one of those UI elements that aren't quite
-  keyboard-friendly. As usually this information is shown just as well
-  in the echo area, this is not necessary.
+   #+BEGIN_SRC emacs-lisp
+     (scroll-bar-mode -1)
+   #+END_SRC
 
-  #+BEGIN_SRC emacs-lisp
-    (tooltip-mode -1)
-  #+END_SRC
+** Blinking cursor
+
+   I suppose a blinking cursor doesn't get lost very easily. But on
+   the other hand, it can induce quite a few more headaches.
+
+   I've noticed that I don't really lose my cursor position all that
+   much, really, so there doesn't seem to be any point in making it
+   blink. Here we go again: It has got to go.
+
+   #+BEGIN_SRC emacs-lisp
+     (blink-cursor-mode -1)
+   #+END_SRC
+
+** Column and line numbers
+
+   As I'm currently using svg-mode-line-themes[fn:2] for my ~mode-line~ I
+   don't need to show these. Also I didn't really use them much, I
+   don't often need to know what line I'm on.
+
+   #+BEGIN_SRC emacs-lisp
+     (column-number-mode -1)
+     (line-number-mode -1)
+   #+END_SRC
+
+** Tooltips
+
+   Tooltips are another one of those UI elements that aren't quite
+   keyboard-friendly. As usually this information is shown just as well
+   in the echo area, this is not necessary.
+
+   #+BEGIN_SRC emacs-lisp
+     (tooltip-mode -1)
+   #+END_SRC
 
 * Add org-mode appointments to the diary
 
@@ -124,9 +158,8 @@
 * Stumpwm integration
 
   This variable, macro and function help with integrating Emacs and
-  Stumpwm. They are used by several other functions to make the two
-  seem extra connected. An example of this can be found in [[Fall back
-  on stumpwm when moving around]].
+  Stumpwm. They are used by some other functions to make the two seem
+  extra connected.
 
   #+BEGIN_SRC emacs-lisp
     (defvar oni:stumpish-program
@@ -148,23 +181,23 @@
       (call-process oni:stumpish-program nil nil nil (format "echo %s" message)))
   #+END_SRC
 
-* Fall back on stumpwm when moving around
-
-  Using the function specified in [[Stumpwm integration]] wrap the
-  =windmove-do-window-select= function and catch any error produced,
-  hoping it's the error that there's no more window to move to and
-  then request that stumpwm move the focus in the same direction as
-  windmove would have.
-
-  #+BEGIN_SRC emacs-lisp
-    (defadvice windmove-do-window-select
-        (around oni:windmove-stumpwm activate)
-      "If no window can be moved to, move stumpwm."
-      (condition-case err
-          ad-do-it
-        (error (oni:stumpwm-command
-                (format "move-focus %s" (ad-get-arg 0))))))
-  #+END_SRC
+** Fall back on stumpwm when moving around
+
+   Using the function specified in [[Stumpwm integration]] wrap the
+   =windmove-do-window-select= function and catch any error produced,
+   hoping it's the error that there's no more window to move to and
+   then request that stumpwm move the focus in the same direction as
+   windmove would have.
+
+   #+BEGIN_SRC emacs-lisp
+     (defadvice windmove-do-window-select
+         (around oni:windmove-stumpwm activate)
+       "If no window can be moved to, move stumpwm."
+       (condition-case err
+           ad-do-it
+         (error (oni:stumpwm-command
+                 (format "move-focus %s" (ad-get-arg 0))))))
+   #+END_SRC
 
 * Don't just quit Emacs with {{{key(C-x C-c)}}} in the daemon
 
@@ -201,7 +234,7 @@
 
   One of the caveats of using two (or more) languages in a single
   installation of Gnus is that ispell sometimes gets confused. Having
-  come across a stackoverflow question[fn:2] about just this subject
+  come across a stackoverflow question[fn:3] about just this subject
   it was easy to modify the source code posted there to come up with
   this.
 
@@ -328,6 +361,11 @@
 
 * Footnotes
 
-[fn:1] https://github.com/sabof/svg-mode-line-themes
+[fn:1] This runs =tmm-menubar=, which lets you navigate the menubar in a
+  text-driven way. I don't ever use it because I know what all my
+  favorite functions are called, but it seems a great deal more
+  efficient than having to click on everything.
+
+[fn:2] https://github.com/sabof/svg-mode-line-themes
 
-[fn:2] http://stackoverflow.com/questions/22175214/automatically-switch-language-in-gnus-depending-on-recipient
+[fn:3] http://stackoverflow.com/questions/22175214/automatically-switch-language-in-gnus-depending-on-recipient