Fork me on GitHub
#cursive
<
2017-07-09
>
cfleming08:07:54

@onetom Right, there’s a problem when running tests in background threads - it doesn’t work right now, but hopefully will very soon.

onetom08:07:41

i was also wondering if it's possible to just see all the errors on the console, but haven't found any such options

onetom08:07:21

is that on purpose? because thanks to the Re-run last test action in REPL action im often in implementation, change then re-run the tests

onetom08:07:10

while i could just almost have a lein test auto, I can't tell that quickly which namespace or which specific test do i want to run...

onetom09:07:47

i had such a workflow when i was using ruby from sublime so im still puzzled that i couldn't replicate the same convenience with clojure (without emacs :)

rauh09:07:57

Can I use connect to a lumo repl with Cursive?

joelsanchez13:07:40

@rauh tried with lumo -n 127.0.0.1:7777 and Cursive's "remote REPL" run configuration, but it seems that Lumo does not support nREPL: https://github.com/anmonteiro/lumo/issues/171

rauh13:07:11

@joelsanchez Thanks! I figured it's not working yet.

joelsanchez13:07:55

start a Lumo socket REPL with the -n argument

joelsanchez13:07:10

then choose “Use clojure.main in normal JVM process” in cursive

joelsanchez13:07:26

and then

(require 'tubular.core)
(tubular.core/connect 5555)

joelsanchez13:07:28

hey @rauh i tried Tubular and it is working flawlessly, let me know if you have problems

rauh13:07:54

@joelsanchez Woah that's nice! I'll try it later, gotta run 🙂

cfleming21:07:32

@joelsanchez @rauh yes, Tubular is currently the best solution.

cfleming21:07:44

I’m planning native Lumo support soon though.

cfleming22:07:09

I’m planning to fix that too in the current round of test improvements.