@katox Hmm. I’ll try to reproduce this, although I’m pretty sure it’s always worked for me.

@bfabry Sorry 😞. I think that’s an IntelliJ bug, but I haven’t seen it for ages.

I searched for it in their YouTrack a while ago but couldn’t find anything.

It’s a hard one to describe though, it’s possible there’s one in there somewhere.

yeah having the same issue finding anything

@bfabry Do you find that if you then close the Java file and open a Clojure one that the splits come back?

yup

just switching back to a clojure file without closing the java file even

@bfabry it's indeed an IntelliJ bug and it's fixed in the latest EAPs

Hi! We (my team) have used Cursive for nearly three months now. For me it’s really slow to debug. It has been like this sporadically, but the last days it is like this all the time. To go from one break-point to another takes 10-20 seconds when it should take a fractions of a second. I gets a little better if I restart IDEA, but after a while it gets really slow again. I can’t hardly work. We don’t have much code < 5.000 LOC. I use Clojure 1.9, maybe that is the problem? Or the memory settings, I don’t know.

@stijn Oh, that’s why I haven’t seen it, I’m on 2016.3 EAP

there were at least 5 tickets when I searched for it

but can't find it back right now 🙂

@bfabry: if you're not OK switching to EAP, you can enable editor tabs again

@teng Yes, unfortunately the debugging is very slow sometimes. I have some ideas about why this is, but it’s extremely difficult to actually identify the problem (you can’t profile or anything like that). I believe it’s to do with the number of classes that have to be searched when a breakpoint is hit, but I don’t know why sometimes it’s much worse than others.

@cfleming I think one way to reproduce that bug is to create a test where the is-form is on the very last line of the test file.

that solves the issue, but it works a bit different

Unfortunately JDI really wants to know the class a breakpoint is set on, and in Clojure that’s basically impossible to determine.

So I have to tell it that the breakpoint might be in any class generated from that namespace.

@cfleming ok - then I will only use the debugger when I really need it! (until it's fixed)

My theory is that this is very slow, but I can’t really test that.

@katox Interesting, I’ll try that, thanks.

@cfleming I was working in a namespace with a :reload-all in the ns. Maybe that made things harder for Cursive and made things go slower.

@teng my colleague uses IDEA 216.2.5 Ultimate edition and he has no problems. I use IDEA 216.2.5 Community edition. Maybe that can make some differences too.

ah, interesting. I wonder if I can get EAP builds when on community edition

I hate how intellij does that thing where it leaves the old version around

yay! switching to eap stopped it

of course now I have tool tips bleeding across desktops somehow

2016.3 looks cool though, particularly like the named args sugar

colin any change of that fancyness ending up in cursive?

@bfabry Yes, absolutely, I looked into it and it’s not hard to do.

oh wow that would be pretty amazing 🙂

Any suggestions for other things you might want to see labeled are also welcome

man, when I think about that feature it's actually amazingly awesome. kwargs are objectively better for readability than positional, but they're annoying to type and take up a lot of space. this solves both those issues

haven't got any thoughts on other things that could be labelled off the top of my head, but I'll keep an eye out