about summary refs log tree commit diff
path: root/emacs/.emacs.d/wpc/buffer.el
diff options
context:
space:
mode:
authorWilliam Carroll <wpcarro@gmail.com>2020-09-01T12·44+0100
committerWilliam Carroll <wpcarro@gmail.com>2020-09-01T13·00+0100
commit718899c629bb1b8bd05285c2e8c5a1709e8e5226 (patch)
treebd360e7b7779e8d8f05df3eb1059887ede6ed8c7 /emacs/.emacs.d/wpc/buffer.el
parent3b2fffe954e3927673e403ee124a78f78bb1c45c (diff)
More Elisp linting
In order for this to scale, I need to solve two things:
1. Ad-hoc ignore fill-column rules for URLs and other exceptions.
2. Run Elisp flychecker without evaluating my Elisp code and firing its
   side-effects.
Diffstat (limited to 'emacs/.emacs.d/wpc/buffer.el')
-rw-r--r--emacs/.emacs.d/wpc/buffer.el4
1 files changed, 2 insertions, 2 deletions
diff --git a/emacs/.emacs.d/wpc/buffer.el b/emacs/.emacs.d/wpc/buffer.el
index de0c2ad66bcd..8494bfa8fb74 100644
--- a/emacs/.emacs.d/wpc/buffer.el
+++ b/emacs/.emacs.d/wpc/buffer.el
@@ -18,7 +18,7 @@
 ;; buffers":
 ;; 1. Toggling previous: <SPC><SPC>
 ;; 2. Using `ivy-read': <SPC>b
-;; TODO: These obscure evil KBDs. Maybe a hydra definition would be best?
+;; TODO: These obscure evil KBDs.  Maybe a hydra definition would be best?
 ;; 3. Cycling (forwards/backwards): C-f, C-b
 
 ;;; Code:
@@ -117,7 +117,7 @@ Return a reference to that buffer."
 ;; encapsulates all of this behavior.
 
 (defun buffer-cycle (cycle-fn)
-  "Cycle forwards or backwards through `buffer-source-code-buffers'."
+  "Using CYCLE-FN, move through `buffer-source-code-buffers'."
   (let ((last-called (source-code-cycle-last-called
                       buffer-source-code-cycle-state))
         (cycle (source-code-cycle-cycle