maurice/snix
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Redefine >> macro as >-> in >.el

Browse source 
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.
This commit is contained in:
William Carroll 2020-09-01 16:26:39 +01:00
parent 718899c629
commit 75a9a156a0
8 changed files with 53 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

13
emacs/.emacs.d/wpc/alist.el
View file

@ -60,21 +60,18 @@
;; TODO: Include a section that compares alist.el to a.el from
;; github.com/plexus/a.el.
;; Dependencies:
;;; 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