about summary refs log tree commit diff
path: root/emacs/.emacs.d/wpc/scope.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/scope.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/scope.el')
-rw-r--r--emacs/.emacs.d/wpc/scope.el6
1 files changed, 3 insertions, 3 deletions
diff --git a/emacs/.emacs.d/wpc/scope.el b/emacs/.emacs.d/wpc/scope.el
index c97a59b88b..e8a2ad2ecc 100644
--- a/emacs/.emacs.d/wpc/scope.el
+++ b/emacs/.emacs.d/wpc/scope.el
@@ -20,7 +20,7 @@
 (require 'alist)
 (require 'stack)
 (require 'struct)
-(require 'macros)
+(require '>)
 
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 ;; Create
@@ -47,7 +47,7 @@ The newest bindings eclipse the oldest."
   "Push a new, empty scope onto XS."
   (struct-update scope
                  scopes
-                 (>> (stack-push (alist-new)))
+                 (>-> (stack-push (alist-new)))
                  xs))
 
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
@@ -75,7 +75,7 @@ The newest bindings eclipse the oldest."
   "Set value, V, at key, K, in XS for the current scope."
   (struct-update scope
                  scopes
-                 (>> (stack-map-top (>> (alist-set k v))))
+                 (>-> (stack-map-top (>-> (alist-set k v))))
                  xs))
 
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;