Fork me on GitHub
#planck
<
2016-11-17
>
bherrmann16:11:58

Howdy. How is "$ planck my.cljs" different from "$ planck -c $PLANCK_CLASSPATH my.cljs"

bherrmann16:11:10

the second version works - the first fails - but I thought they would be the same

mfikes16:11:47

@bherrmann Does my.cljs try to load things that would be in the classpath?

bherrmann16:11:50

(ns my (:require [cmd.util :refer [prop]]))

bherrmann16:11:57

something like that... so yes.

mfikes16:11:33

@bherrmann When you run planck my.cljs it should complain about an inability to load the source for cmd.util

bherrmann16:11:05

yes, it gives that error on the first version, no error on the second version.

bherrmann16:11:37

I should mention too, that my.cljs has the #!/usr/bin/env planck as its first line.

bherrmann16:11:55

so normally it is used directly via bash.

bherrmann16:11:57

my workaround, that I just found, is to simply use "#!/usr/bin/env planck -c /full/path/to/libs"

bherrmann16:11:16

and not use PLANCK_CLASSPATH as it is ineffective

bherrmann16:11:49

im running planck 1.6 via brew

bherrmann16:11:56

did it predate PLANCK_CLASSPATH?

mfikes16:11:23

@bherrmann I apologize, the mistake is that I’ve published the master docs to the website. Will fix that now. PLANCK_CLASSPATH support hasn’t been released yet.

bherrmann16:11:44

Thats what I'm seeing 🙂

bherrmann16:11:09

no worries. Thanks for working on this thing - I love it.

mfikes16:11:34

If you really want that, you’d have to build master for yourself. Otherwise passing -c works with older versions.

bherrmann17:11:19

Thanks! I can work with out it for now. Cheers

mfikes17:11:50

@bherrmann If you refresh, the docs are now consistent with the Planck 1.17 release (the latest)