Clojurians Log v2

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

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

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

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

something like that... so yes.

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

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

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

so normally it is used directly via bash.

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

and not use PLANCK_CLASSPATH as it is ineffective

im running planck 1.6 via brew

did it predate PLANCK_CLASSPATH?

@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.

Thats what I'm seeing 🙂

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

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

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

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