Fork me on GitHub
#cursive
<
2020-03-05
>
imre13:03:04

Anyone using cursive with ij2020.1 eap? How is it working out for you?

markaddleman14:03:13

I'm using it without any problems

onetom18:03:32

me too. i've experienced some minor issues, like if i change some extra-paths in my project's deps.edn, i had to close and re-open the project window; simply refreshing the deps is not enough. i was also running 3 repls (from a monorepo) and none of them accepted my cmd-shift-l to load a file, but after re-starting the corresponding repl it started to work again. small things like that might happen, but haven't seen any exceptions since i've installed eap9

cfleming23:03:58

@U086D6TBN The refresh issue is https://github.com/cursive-ide/cursive/issues/2331, which I’ve just fixed for the next EAP.

cfleming23:03:39

I’m also using Cursive with 2020.1 BTW.

imre08:03:00

Cheers lads. I started using it yesterday, no issues so far.

👍 4
kenny16:03:33

Why would this occur?

cfleming21:03:28

I don’t know, I think that’s an IntelliJ error. Is there anything in the logs?

kenny23:03:38

I don't see anything. It seems to happen somewhat often.

kenny23:03:02

It may be related to the object being a lazyseq.

kenny20:03:59

I am still hitting this and there is no line in the logs. Is there a way to turn on further logs to try and see what's going on?

kenny20:03:52

I'm tail -F'ing the log while repro'ing the "Internal error, see logs for more details" issue and nothing. Haven't been able to see any pattern other than it only happens when the object is some sort of a list.

markaddleman19:03:33

Cursive does a nice job of suggesting keywords when I type : However, it does not suggest when I'm in a destructing context like {:keys [key1 key2]} . Can Cursive detect that context and suggest keywords without prefixing the destructing with a colon?

12
petterik19:03:15

Same with {:<namespace>/keys [key1 key2]}

👍 4
cfleming21:03:46

Yes, I have plans to do both of these.

👏 8
grav20:03:23

Seems remote nrepl with “use port from repl file” is still broken. I just commented on the old issue: https://github.com/cursive-ide/cursive/issues/2311

cfleming21:03:53

Hmm, I was just using that yesterday, I’ll try to reproduce that.

cfleming04:03:21

This is fixed in 1.9.1-eap10, out now.

grav05:03:38

Thanks a lot Colin! The error message in eap10 made me realize there was no .nrepl-port file. Found out that shadow-cljs creates it as .shadow-cljs/nrepl-port. Anyway, a ln -s fixed it. https://github.com/thheller/shadow-cljs/issues/524#issuecomment-510365911

dmarjenburgh07:03:41

Had the same issue a few days back. Is there a way to tell cursive the location of the nrepl-port file?