Fork me on GitHub
#cider
<
2017-11-11
>
psimon09:11:06

Hi all. Is there a way to break cider debugger on exception, like Cursive allows me to?

dominicm09:11:16

@psimon I don't use it, so I'm not certain, but my understand is no. I think this allows you to achieve the same thing though: https://github.com/prismofeverything/schmetterling

psimon09:11:16

Thanks! Will have a look.

bhauman15:11:35

hmmm how do I see the cider message buffer now?

dpsutton15:11:40

@bhauman do you mean the nrepl logging?

dpsutton15:11:57

nrepl-toggle-message-logging

bhauman15:11:04

there used to be a buffer with all the messages

bhauman15:11:11

that will do it

bhauman15:11:19

I looked for that and didn't find it

dpsutton15:11:31

yeah i always look for a cider prefix and forget its nrepl

bhauman15:11:31

I probably need to upgrade

dpsutton15:11:41

oh. you don't see that?

bhauman15:11:43

oh yeah nrepl

bhauman15:11:52

that was my confusion as well

dpsutton15:11:06

it may have been on by default in a past version

bhauman15:11:40

yeah, I've written a replacement for piggieback that hosts its cljs on a thread

bhauman15:11:08

which makes it just as responsive as the shell repl, or lumo

bhauman15:11:25

trying to work out the last few bugs

dpsutton15:11:32

if i can help let me know

bhauman15:11:49

thanks man!

dpsutton15:11:50

and that sounds really really awesome

dpsutton15:11:52

and complicated

dpsutton15:11:01

yeah if you have any questions feel free to directly ping me here

dpsutton15:11:05

or message whatever

bhauman15:11:10

thanks again

bhauman15:11:49

@dpsutton any reason c-x c-e inside a ClojureScript buffer would get redirected to the Clojure REPL connection, when I'm not using piggieback? Is cider looking specifically for piggieback vars?

dpsutton15:11:32

yeah. there have been some changes to the "choose connection" logic that i don't like

dpsutton15:11:43

bring up your cljs repl and evaluate something simple in it like (+ 1 1)

dpsutton15:11:46

and then try again

dpsutton15:11:01

somewhere if it can't decide which connection to use it uses the last one

bhauman15:11:10

I think something else is going on... I'll come back with a more specific question

dpsutton15:11:29

ok. one other thing to check is the session id's in the nrepl traffic

bhauman15:11:42

yeah they are different and it seems like all buffer traffic is going to the Clojure nREPL connection

bhauman15:11:54

this isn't the case when I use piggieback

bhauman15:11:21

which makes me think that there is piggieback detection going on

bhauman15:11:55

but I don't see messages that do any such thing

dpsutton16:11:13

i don't even know where to begin looking into that

bhauman16:11:19

no worries

dpsutton16:11:20

let me crank up something and watch the traffic

bhauman16:11:14

lots of piggieback specific stuff in there

bhauman16:11:08

which is pretty dissappointing

dpsutton16:11:41

i'm looking at it and wondering if there is a way to describe a contract that any bridge like piggieback could satisfy

bhauman16:11:52

the bottom line is that they need the compiler environment which makes complete sense