Fork me on GitHub
#calva
<
2020-01-03
>
sjharms16:01:39

Cross posting here: does anyone use clojure.tools.logging with Calva? https://clojurians.slack.com/archives/C17JYSA3H/p1578037204012000

smashedtoatoms17:01:15

I find that they show up in the terminal, not the repl.

smashedtoatoms17:01:32

Check your terminal that calva spins up and you'll likely see your log messages in there.

sjharms17:01:00

Ah I was watching ‘Calva Says’, I will check that out

sjharms17:01:18

Interesting that the Taoensso messages don’t go to my terminal window, but do get captured via Calva Says

smashedtoatoms17:01:28

Yea, it was unexpected for me initially, but if you think about it, stdout is the terminal, not the repl.

smashedtoatoms17:01:01

I don't fully understand what is going on, so I can't explain it yet.

smashedtoatoms17:01:13

I am fairly new to clojure and repl dev, so there are still quite a few surprises for me.

sjharms17:01:36

Thank you for the pointer though, it was really helpful

smashedtoatoms17:01:49

I actually barely use the actual repl output. I basically leave the terminal open, and do everything in (comment ...) inside of the editor.

smashedtoatoms17:01:58

Not sure if that is correct or not, but it's fast for me.

smashedtoatoms17:01:05

When I get better, I will probably make a video of myself doing something in the repl, because I feel like reading about it doesn't do it justice. Until I started doing it, I didn't really get why people like it.

sjharms17:01:06

In this case I am aspirationally hoping to fire off async tasks which write to a database, and it feels like anything which doesn’t return immediately is hard to do that with

smashedtoatoms17:01:51

Yea, if they return futures or promises then you'll just get the unresolved result back, so logs would definitely be helpful.