@clark I’m hoping to do this soon, since lots of people are asking for it.

I don’t have a public roadmap, but I’m working on that too.

@jasonjckn Sorry, I missed your message earlier. See here: https://cursive-ide.com/userguide/repl.html under “Interaction with the editor"

Anybody having any problems doing Clojure with Cursive on Mac OS Sierra?

@pupeno I’m not aware of any

@cfleming are you running Mac OS Sierra?

No, I’m not, but no-one has reported issues

I will be running it soon, though

I’ll wait till then… 😉 I’m becoming conservative lately.

Hehe, especially since there doesn’t seem to be a compelling reason to upgrade

@pupeno @cfleming I have been running Cursive on Mac OS Sierra for a while now and have had no issues.

Good to know.

No issues on sierra here either

I have been getting some extreme lag while typing in the REPL. If I try typing the same code in the editor I have no latency.

It seems like the REPL latency occurs when the code is multiline

@kenny Are you on the 1.4.2 EAP?

1.4.2-eap1-2016.3

Ok, I thought it might have been the memory issues fixed in that build.

Anything else funky in your project/setup I should know about? Is that a remote REPL?

Yeah. Remote REPL using the lein port. It is connected to a boot repl

It gets to the point where it is completely unusable to type in the REPL. I just end up editing the form in the editor and using the send form to REPL command.

Can you see anything in the task manager? CPU use in the IDE/server process? What about memory use in the IDE? IIRC you have the memory widget on, right?

It also freezes the entire IntelliJ. So if I try editing something in the REPL pane I can’t click or type anywhere else until it unfreezes

Interesting, so it’s something blocking the EDT. Can you check for automatic thread dumps? https://intellij-support.jetbrains.com/hc/en-us/articles/206544899-Getting-a-thread-dump-when-IDE-hangs-and-doesn-t-respond

Yeah memory widget is on. It’s at about 300mb out of 4gb.

I’ve had it happen before where the REPL gets really slow but the memory usage also spikes. The most recent update seems to have fixed that though.

Yeah, that was what I suspected, but if you’re already on that build then it must be something else.

I’ll try the thread dump right now

Ok, do check for the automatic ones, too.

I’ll send in PM

Ok, or even better by email

What’s the email again?

They won’t get eaten by the slack God then.

<mailto:[email protected]|[email protected]>

Lots of automatic freeze dumps 😛

Hehe, good good

Just some recent ones that you think coincide with the problem would be good.

Sent

Actually I take it back. It still happens when the text is only on one line.