https://github.com/clojure-emacs/cider/issues/3055#issuecomment-1736099756 is the approach I intend to get into cider, as far as tapping is concerned I'd be wary of tapping everything. While it doesn't sound disastrous, it's also not the sort of thing that we should officially foster

fine for me. Users can do it on "own risk"

I read over the discussions, and can now give my comment here, more about my "request". One question is if / if not CIDER should have "support" for easely "tapping" everything. In my view this is a yes/no question, no further config. Either it "taps" nothing "on evaluation", as now. Or it allows easely to "tap everything". This has indeed a certain "risk" of exploding memory, so fore sure should be disabled by default. It is of course already "easy", as my snippet shows. The second question is, if CIDER should make it more easy to add tap handlers, and if / if not something should happen automatically when epl starts. Maybe it helps as well to think about my initial use case, which is to "keep a visual list of all past evaluations results", which CIDER does not have at all as feature. (+ it allows me to have that list rendered in Browser, so having richt output)

CIDER supports this in some form, but only of the last three results, just as Clojure does.

Having an option in cider that sends nrepl eval results to any registered tap source could simplify tool uses, although it seems the main tap tools already support nrepl evals. Portal data inspector works very well when tapping via nrepl middleware, automatically sending all evaluation results to Portal and keeping a full history ( Portal clear command will remove history if required) https://cljdoc.org/d/djblue/portal/0.37.1/doc/guides/nrepl I also send mulog log event message to Portal with a custom mulog event publisher that taps every log event. I enable this configuration and launch portal via a https://practical.li/clojure/data-inspector/portal/#editor-commands, so it can be selectively enabled when starting the repl.

Indeed, middleware is an other option. I was searching once for a generic nrepl middleware which is simply "tapping" all results, but did not find any.

It should be reasonably easy to implement a custom piece of middleware and add it to your stack This also may answer your second question - given a smart enough piece of nREPL middleware, it could be configured to satisfy diverse needs easily.

thanks vemv

Yes, we've worked specifically on it very recently Do you not see an overlay? It may be some setting, can check if you don't find it first :)

I checked https://docs.cider.mx/cider/usage/dealing_with_errors.html#configuration but didn't see a setting

I only see messages in the minibuffer

The logic for deciding whether an overlay is displayed is as follows:

(or
 ;; if we won't show *cider-error*, because of configuration, the overlay is adequate because it compensates for the lack of info in a compact manner:
 (not cider-show-error-buffer)
 (not (cider-connection-has-capability-p 'jvm-compilation-errors))
 ;; if we won't show *cider-error*, because of an ignored phase, the overlay is adequate:
 (and cider-show-error-buffer
      (member phase cider-clojure-compilation-error-phases)))

And it looks like this:

I'm stumped. cider-version is 1.8.2 Geneva, cider-show-error-buffer is t (tho I also tried with nil), m-x : (cider-connection-has-capability-p 'jvm-compilation-errors) => nil. Yet I still see no overlay. i'm using cider-eval-last-sexp

What about cider-eval-sexp-at-point ?

nvm, i got it — another part of my config was setting cider-use-overlays which I guess is also in the logic chain somewhere

👍 . If you feel cider-use-overlays is too coarse-grained for your preferences, I'd be happy to discuss it over GH

https://github.com/clojure-emacs/cider/issues/3522