From 75a9a156a0fab425ccc6821d38d7d20d0c2aba31 Mon Sep 17 00:00:00 2001 From: William Carroll Date: Tue, 1 Sep 2020 16:26:39 +0100 Subject: 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. --- emacs/.emacs.d/wpc/alist.el | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) (limited to 'emacs/.emacs.d/wpc/alist.el') diff --git a/emacs/.emacs.d/wpc/alist.el b/emacs/.emacs.d/wpc/alist.el index 52493c6c03a7..dd4b10133d53 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 -- cgit 1.4.1