about summary refs log tree commit diff
path: root/emacs/.emacs.d/wpc/alist.el
diff options
context:
space:
mode:
authorWilliam Carroll <wpcarro@gmail.com>2020-09-01T15·26+0100
committerWilliam Carroll <wpcarro@gmail.com>2020-09-01T15·26+0100
commit75a9a156a0fab425ccc6821d38d7d20d0c2aba31 (patch)
treea17ab9db0cac258633177a9cb9f6be302fbf3610 /emacs/.emacs.d/wpc/alist.el
parent718899c629bb1b8bd05285c2e8c5a1709e8e5226 (diff)
Redefine >> macro as >-> in >.el
I created a strangely named Elisp module, >.el, just to appease the CI gods. My
gut tells me that this is a desperate idea and fails the smell test. I'm pretty
eager to pass the linting phase of my Elisp CI, however, and I can always revert
this.
Diffstat (limited to 'emacs/.emacs.d/wpc/alist.el')
-rw-r--r--emacs/.emacs.d/wpc/alist.el11
1 files changed, 4 insertions, 7 deletions
diff --git a/emacs/.emacs.d/wpc/alist.el b/emacs/.emacs.d/wpc/alist.el
index 52493c6c03..dd4b10133d 100644
--- a/emacs/.emacs.d/wpc/alist.el
+++ b/emacs/.emacs.d/wpc/alist.el
@@ -60,21 +60,18 @@
 ;; TODO: Include a section that compares alist.el to a.el from
 ;; github.com/plexus/a.el.
 
+;;; Code:
+
+;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 ;; Dependencies:
+;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 
-;; TODO: Consider dropping explicit dependency white-listing since all of these
-;; should be available in my Emacs.  The problem arises when this library needs
-;; to be published, in which case, something like Nix and a build process could
-;; possible insert the necessary require statements herein.  Not sure how I feel
-;; about this though.
 (require 'maybe)
 (require 'macros)
 (require 'dash)
 (require 'tuple)
 (require 'maybe)
 
-;;; Code:
-
 ;; TODO: Support function aliases for:
 ;; - create/set
 ;; - read/get