Clojurians Log v2

if it works like it used to, each form you evaluate has an id, and that way it’s clear which form causes prints. and when the form finally returns it is marked as done and removed from a list of sent forms and their associated response handlers.

this sounds like something was completed but whatever it spawned keeps printing

you can do m-x nrepl toggle message logging or whatever it is. it’s something along those lines. restart your repl and then you should be able to find whatever form originally was 49, or whatever id it will be

Thanks, will try that

Is there a way to increase the number of messages that are kept on the log? by the time it happens the message has been deleted.

Seems like it’s this one…

(-->
  id                             "22"
  op                             "eval"
  session                        "29c7df83-fbbd-4a08-8200-1ba695fdd9bd"
  time-stamp                     "2026-07-28 14:52:24.662362000"
  code                           "(bardo.init/all!)
"
  ns                             #("tieminos.habitat.extended-sections.tunel-cuantico-bardo.main" 0 60 (face font-lock-type-face help-echo cider--help-echo fontified t))
  file                           "/Users/diego/Music/code/tieminos/src/tieminos/habitat/extended_sections/tunel_cuantico_bardo/main.clj"
  line                           25
  column                         3
  nrepl.middleware.print/print   "cider.nrepl.pprint/pr"
  nrepl.middleware.print/stream? nil
  nrepl.middleware.print/options (dict
                                   length 100)
  nrepl.middleware.print/quota   1048576
)

I think you’ve hit an edge case when it comes to long-lived output producers. I’ve tried to address it here https://github.com/clojure-emacs/cider/pull/4150 You can try it out and let me know if that solved the problem for you.

Thank you very much, will try this later today and report back.

Seems to be working fine, thanks again for addressing the edge case