Fork me on GitHub
#cider
<
2018-12-20
>
puzzler08:12:42

Is there a parinfer 2 implementation for emacs?

orestis09:12:48

I’m having trouble wrapping my head around how I can get CIDER to connect to two different nREPL servers at the same time, within the same project. I am running my nREPL servers outside of CIDER: One is a plain Clojure server, the other is shadow-cljs. I can connect to either one of them and the correct thing happens, but when I try to connect at both, suddenly things start to fall apart. I’ve read the http://www.cider.mx/en/latest/managing_connections/ many times and I still can’t figure out how to do it. Any pointers welcome 🙂

orestis09:12:33

As I understand it, I need to have two different “sessions”, since my sessions won’t share the same nREPL server.

orestis09:12:07

So I need to do both cider-connect-clj and cider-connect-cljs. I do that, and sesman does report the two sessions running independently.

orestis09:12:13

I tried to link a session with a buffer, and i see the link in sesman, but still I can’t get the expected results — evaluating to my CLJS buffer seems to hang or do something weird.

orestis09:12:39

Using the shadow-cljs graphical REPL (in the build server webpage) produces the expected results so the nREPL connection is working. Apparently not an indicator, the build-browser repl is not using nREPL.

thheller09:12:17

FWIW the built-in REPL doesn't use nREPL

orestis09:12:01

Oh, it shows a list of nREPL-like connections so this is what I assumed.

thheller09:12:19

nah it directly talks to the internals which are a layer below nrepl

orestis09:12:46

Thanks for the clarification.

orestis09:12:35

I tried to follow the instructions on the manual but it seems the commands indicated there are named something different in CIDER 0.18 — I’d file a PR to change them but perhaps best to first figure this out 🙂

0atman14:12:55

afternoon gang. Can someone advise me how to use cider debugging inside a deftest?

0atman14:12:00

as you see, my tests are wrapped in a let, which gets debugged as normal: I can hit c to move through the forms until it gets to the deftest

0atman14:12:36

then the debugger quits, and my-test is highlighted in red, ready to be debugged when run. When I run it with , t t it doesn't debug, it passes as normal

onecoder4u14:12:24

Newbie here. I'm getting an error when trying to run coder-jack-in. I'm able to start the repl manually via lein and cider-connect to it. the error is Error loading refactor-nrepl.middleware

onecoder4u14:12:18

I'm using emacs-live to setup everything

onecoder4u14:12:51

A couple things I tried, I deleted my profile file.

onecoder4u14:12:07

I tried the following specifying the following plugins cider/cider-nrepl "0.12.0", refactor-nrepl "2.2.0"

dpsutton14:12:58

ah. you are following the clojure for the brave and true setup?

dpsutton14:12:29

cider 0.12 is about 4 years old. current version is 0.18

onecoder4u14:12:32

no, i'm used the emacs-live overtone setup for clojure

onecoder4u14:12:53

Would you recommend using the "clojure for the brave and true" setup ? or is there another one?

dpsutton14:12:03

no i thought that was what was giving you issues 🙂

onecoder4u14:12:42

ok ty, i'll take a look and see if that gets me going in the right direction.

dpsutton15:12:13

for sure 🙂 sorry it can be so complicated. i would recommend dropping refactor stuff until you have a known working repl and then add it in

onecoder4u15:12:52

trying to figure out now why cider version is 0.14.

onecoder4u15:12:32

I don't see any thing specifying that version.

mhcat17:12:06

after upgrading to leiningen 2.8.3 I'm seeing this trying to start a repl:

Warning: implicit middleware found: refactor-nrepl.plugin/middleware \nPlease declare all middleware in :middleware as implicit loading is deprecated.\

mhcat17:12:51

the repl doesn't start, this is caught by the emacs debugger which I have switched on for errors

mhcat17:12:25

ok I fixed the repl by fixing unrelated symbol resolution issues

jumar17:12:58

@tristram I also have issues to debug tests when run via cider utilities. However, using (clojure.test/run-tests ) works. See here: https://stackoverflow.com/questions/53870654/use-cider-debugging-inside-a-deftest/53873709#53873709

0atman18:12:36

many thanks @jumar, that is a great workaround

0atman18:12:52

I can't believe we're the only ones to want to debug inside a test, though - right?!

jumar18:12:46

To be honest, I faced this issues several times and just gave up. Your SO question made me thinking and find at least the workaround pretty quickly 🙂