This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-24
Channels
- # announcements (3)
- # babashka (23)
- # beginners (35)
- # cider (3)
- # clara (3)
- # clj-kondo (14)
- # cljdoc (1)
- # cljs-dev (1)
- # clojure (82)
- # clojure-austin (9)
- # clojure-europe (5)
- # clojurescript (23)
- # conjure (62)
- # cursive (73)
- # defnpodcast (1)
- # emacs (3)
- # ethereum (1)
- # gratitude (1)
- # hyperfiddle (12)
- # introduce-yourself (1)
- # leiningen (2)
- # lsp (44)
- # malli (7)
- # polylith (2)
- # portal (17)
- # re-frame (5)
- # reitit (3)
- # sci (8)
- # shadow-cljs (5)
- # tools-build (11)
Currently the inspect multimethod is behind cider.nrepl.inlined-deps.orchard.v0v9v2.orchard.inspect
, and I am concerned that extending the inspect multimethod in that namespace would break if the orchard dependency version gets bumped. Is there another way to add custom types to the cider inspector?
@bozhidar I would like to write the small PR that adds the possibility of not sending the result of the evaluation to the echo area, as maybe you have more practical means of seeing the results, like portal
or a *cider-result*
buffer always open.
I see that the code is here https://github.com/clojure-emacs/cider/blob/86dd3fee9d9836dcd56f6abb91ba59b7aeedecb9/cider-overlays.el#L286 and it would be easy to just change the condition for that invisible tag, but I'd like to ask about flag organization first:
It seems that the flag cider-use-overlay
is in charge of also deciding if something goes or not in the echo area. Would it be easier to use two cider-use-overlay
and cider-use-echo-area
options, so that each of one does a simple t/nil customization of where the result should go?