This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-17
Channels
- # beginners (10)
- # boot (9)
- # cider (1)
- # cljs-dev (191)
- # clojure (77)
- # clojure-russia (4)
- # clojure-serbia (10)
- # clojure-spec (19)
- # clojure-uk (4)
- # clojurescript (16)
- # core-async (9)
- # cursive (1)
- # data-science (1)
- # datomic (3)
- # emacs (42)
- # graphql (2)
- # hoplon (38)
- # jobs (1)
- # jobs-discuss (18)
- # luminus (3)
- # lumo (20)
- # off-topic (9)
- # om (51)
- # parinfer (3)
- # pedestal (8)
- # re-frame (4)
- # reagent (7)
- # rum (9)
- # sql (9)
- # untangled (81)
it just always seemed so much useless ceremony to me. What's the harm of simply loading it?
related question, is it fair to limit a new package to be only compatible with Emacs 25.1 or up? 🙂
My Travis tests are currently running on 24.3, and already ran into several things. No alist-get
, <=
doesn't have a three-arity version
well the reason people wrap it, is so that your package when byte compiled doesn’t have to depend on cl
…
as for the compatibility with Emacs version, that’s kind of up to you, right ?
most people I know seem to update fairly quickly, but I imagine there's a large contingent that doesn't
every time I write (cdr (assq ))
or (and (<= ?0 char) (<= char ?9))
I want to throw my laptop out the window
thing is it's usually harder to port to the old paradigms than vice versa... I'll see how much pain I can take
I'll see if I can set up a build matrix that does both, so that I can at least make sure 25.1 passes
just realized (eval-when-compile (require 'my-own-hacks))
would allow you to define your own short convenience macros without polluting the global namespace. I wonder if the MELPA people would let that through.
well if https://github.com/purcell/package-lint doesn’t complain, then you’d be good to go
41:1: error: "clj-parse*" doesn't start with package's prefix "clj-parse".
give me a break will ya 😉
anyone using https://github.com/yuya373/emacs-slack ?