chlorine-clover

About Chlorine for Atom and Clover for VS Code: https://atom.io/packages/chlorine and https://marketplace.visualstudio.com/items?itemName=mauricioszabo.clover
Rowan Barnard 2020-08-19T04:04:43.019300Z

Hi guys, not sure if this is Chlorine, Atom or just a general Clojure thing but I was trying to require in clojure.test.check using the (require...) syntax as opposed to (:require...) and it kept giving me a ClassNotFound exception:

Rowan Barnard 2020-08-19T04:05:28.020300Z

As you can see in the screenshot when I required in test.check,properties using the same method it worked

Rowan Barnard 2020-08-19T04:06:41.021500Z

Then when I used the (:require...) as a keyword at the top of the file that evaluated without any problems and I could use the stuff in the test.check namespace:

Rowan Barnard 2020-08-19T04:09:28.024100Z

So really not sure what is going on there? And why the non-keyword require was not working - am using Sean Corfield's deps.edn file with REBL setup just so you know. Any input would be great thanks 🙂

Rowan Barnard 2020-08-19T04:10:59.024900Z

The command-line options I am using to start it up before I connect with Chlorine: clj -A:deps:test:rebl-11-win:socket

seancorfield 2020-08-19T04:26:28.025700Z

I suspect you accidentally did eval-block with you cursor inside the [ .. ] or immediately after it, instead of eval-top-block.

seancorfield 2020-08-19T04:26:47.026200Z

(even tho' your screen shot shows the cursor outside the form)

seancorfield 2020-08-19T04:27:48.027400Z

I can repro your error if I do ctrl-; b (eval-block) with my cursor inside or just after the ]. If my cursor is after the ) it works.

seancorfield 2020-08-19T04:28:33.028400Z

This is because you're trying to evaluate the form [clojure.test.check :as tc] and the symbol clojure.test.check looks unquoted and therefore fails to resolve @flyingpython

Rowan Barnard 2020-08-19T04:31:46.030600Z

Yeah my screenshot I took sometime afterwards, yeah I always try to do the top block but I guess it is easy to miss the shift and get the little b instead so that was probably it then, thanks for helping me understand 🙂

Rowan Barnard 2020-08-19T05:22:25.034100Z

Yes I've tried setting up the same context as before and the non-keyword require is working and throws the same exception when I use lowercase b so it must just have been that I missed the shift key on it as you say, thanks Sean 😉