From 718899c629bb1b8bd05285c2e8c5a1709e8e5226 Mon Sep 17 00:00:00 2001 From: William Carroll Date: Tue, 1 Sep 2020 13:44:18 +0100 Subject: 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. --- emacs/.emacs.d/wpc/buffer.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'emacs/.emacs.d/wpc/buffer.el') 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: ;; 2. Using `ivy-read': 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 -- cgit 1.4.1