Fork me on GitHub
#emacs
<
2017-06-17
>
plexus07:06:19

are you still supposed to wrap (require 'cl) in eval-when-compile?

dotemacs08:06:25

why would you not want to do it @plexus ? 🙂

dotemacs08:06:31

and why not use cl-lib instead?

plexus08:06:46

it just always seemed so much useless ceremony to me. What's the harm of simply loading it?

plexus08:06:57

I'm using case, seems that's not in cl-lib

plexus08:06:41

related question, is it fair to limit a new package to be only compatible with Emacs 25.1 or up? 🙂

plexus08:06:08

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

plexus08:06:32

it least let-alist has an ELPA package but seems there's no backport for alist-get

dotemacs08:06:32

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 ?

dotemacs08:06:55

do you anticipate that there will be a large userbase on 24.3 ?

plexus08:06:09

sure, I just have no idea how many people still use older versions

plexus08:06:49

most people I know seem to update fairly quickly, but I imagine there's a large contingent that doesn't

dotemacs08:06:02

that’s just a guess

dotemacs08:06:41

maybe there should be yearly survey on emacs versions and package usage

dotemacs08:06:50

or maybe more like quarterly

plexus08:06:53

that would be pretty useful

plexus08:06:06

yearly would already be helpful, to get an idea of trends

plexus08:06:36

every time I write (cdr (assq )) or (and (<= ?0 char) (<= char ?9)) I want to throw my laptop out the window

plexus08:06:06

there's no digitp, I checked 🙂

dotemacs08:06:32

well, maybe just target your own need first seeing as it’s open source

dotemacs08:06:42

and then if you get enough complaints …

dotemacs08:06:23

24.3 was released 4 years ago, well more like 3.5 but still

plexus08:06:32

thing is it's usually harder to port to the old paradigms than vice versa... I'll see how much pain I can take

plexus08:06:03

OTOH 25.1 is from last September, that's less than a year...

plexus08:06:47

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

dotemacs08:06:04

you’re testing on TravisCI ?

dotemacs08:06:22

well then you should be pretty good to go…

dotemacs08:06:54

is this unrepl.el related ?

plexus09:06:47

yeah, it's for the parser lib

dotemacs09:06:03

oh, and for case just use cl-case so you can just require cl-lib

dotemacs09:06:30

re clj-parse cool!

plexus09:06:11

ugh why does emacs lisp have to be so ugly? 😭

plexus09:06:35

but thanks, that's a good tip!

plexus09:06:49

learning lots of new things 🙂

plexus09:06:44

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.

dotemacs09:06:23

well if https://github.com/purcell/package-lint doesn’t complain, then you’d be good to go

plexus09:06:28

41:1: error: "clj-parse*" doesn't start with package's prefix "clj-parse". give me a break will ya 😉

dotemacs09:06:35

try clj-parse-* 🙂 It’s probably just a regex in the linter