cider

A channel dedicated to the Clojure Interactive Development Environment that Rocks (aka CIDER). :cider:
blak3mill3r 2021-03-13T01:22:02.259600Z

My favorite old feature... I have some dirty hack that emulates it

blak3mill3r 2021-03-13T01:22:24.259800Z

One repl per emacs instance, the target of all evals

blak3mill3r 2021-03-13T01:23:49.260Z

:cider: thank you, Bozhidar, for making such a power tool!

zane 2021-03-13T06:24:29.260600Z

Anyone have any idea what might be triggering this message when I launch a REPL?

Error killing transient buffer: (error Process nrepl-connection is not a subprocess)

yuhan 2021-03-13T11:27:27.261300Z

you could toggle debug-on-error and examine the stacktrace the next time it appears

zane 2021-03-13T21:07:53.266100Z

Seems like it’s maybe a Doom thing.

zane 2021-03-13T22:49:38.266500Z

Confirmed that this is an issue in Doom in particular.

zane 2021-03-13T22:50:03.266700Z

It’s being fixed upstream, but in the meantime this is a workaround:

(after! cider
  (set-popup-rule! "^*cider-repl" :quit nil :ttl nil))

bozhidar 2021-03-13T08:39:19.260700Z

Thanks! In hindsight I think that adopting Sesman was a huge mistake, but unfortunately it's not easy to undo it. It was supposed to make working with multiple REPL easier, but clearly it made it everything more complex. 😞

yuhan 2021-03-13T11:27:27.261300Z

you could toggle debug-on-error and examine the stacktrace the next time it appears

william 2021-03-13T18:55:03.265400Z

I'm trying to understand some code in clojure-lsp . To do that, I have some test code in emacs instance A, and my checkout of a clojure-lsp server in emacs instance B. Both these emacs instances are connected to an underlying clojure-lsp server via nrepl . I can successfully redefine functions this way. What I would like to be able to do, is using cider-debug-defun-at-point, to see the calls to the functions as they happen. But if I try to invoke that I get errors to the tune of:

clojure.lang.ExceptionInfo: null
#:clojure.error{:phase :read-source}
 at clojure.main$repl$read_eval_print__9110$fn__9111.invoke (main.clj:433)
    clojure.main$repl$read_eval_print__9110.invoke (main.clj:432)
    clojure.main$repl$fn__9119.invoke (main.clj:458)
    clojure.main$repl.invokeStatic (main.clj:458)
    clojure.main$repl.doInvoke (main.clj:368)
    clojure.lang.RestFn.invoke (RestFn.java:1523)
    nrepl.middleware.interruptible_eval$evaluate.invokeStatic (interruptible_eval.clj:84)
    nrepl.middleware.interruptible_eval$evaluate.invoke (interruptible_eval.clj:56)
    nrepl.middleware.interruptible_eval$interruptible_eval$fn__980$fn__984.invoke (interruptible_eval.clj:152)
    clojure.lang.AFn.run (AFn.java:22)
    nrepl.middleware.session$session_exec$main_loop__1048$fn__1052.invoke (session.clj:202)
    nrepl.middleware.session$session_exec$main_loop__1048.invoke (session.clj:201)
    clojure.lang.AFn.run (AFn.java:22)
    java.lang.Thread.run (Thread.java:832)
Caused by: clojure.lang.LispReader$ReaderException: java.lang.RuntimeException: No reader function for tag dbg
is there any way to get what I want? How does cider-debug actually work?

zane 2021-03-13T21:07:53.266100Z

Seems like it’s maybe a Doom thing.

zane 2021-03-13T22:49:38.266500Z

Confirmed that this is an issue in Doom in particular.

zane 2021-03-13T22:50:03.266700Z

It’s being fixed upstream, but in the meantime this is a workaround:

(after! cider
  (set-popup-rule! "^*cider-repl" :quit nil :ttl nil))