Fork me on GitHub
#nrepl
<
2019-01-11
>
bozhidar06:01:15

@jeremy642 To my knowledge Cursive should work just fine with the modern nREPL.

bozhidar06:01:39

Perhaps you’re not on the latest version or something like this?

cfleming07:01:49

@bozhidar Cursive still uses the old one, but IIRC it should be compatible with the new server, right?

cfleming07:01:39

I’ll upgrade the nREPL Cursive uses for the next release, but that will only be for REPLs managed by Cursive - ones started via lein will use whatever version Lein uses.

bozhidar08:01:29

@cfleming It’s compatible on the protocol level, but the middleware is not compatible because of the namespace change.

bozhidar08:01:44

Generally it’s a bad idea to mix them in the same project as some middlewares use conditional requires to figure out which one to load and if some other code loads the unexpected nREPL you get into a situation like Jeremy’s.

bozhidar08:01:41

> I’ll upgrade the nREPL Cursive uses for the next release, but that will only be for REPLs managed by Cursive - ones started via lein will use whatever version Lein uses.

bozhidar08:01:44

That’d be great!

bozhidar08:01:57

Now all tools are using the new nREPL in their current releases. In this situation I’ve decided to remove completely support for tools.nrepl in the projects I maintain and just encourage people to upgrade their boot/lein.