This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-04
Channels
- # announcements (1)
- # architecture (7)
- # beginners (44)
- # biff (11)
- # calva (15)
- # cider (5)
- # clerk (9)
- # clj-kondo (20)
- # clj-on-windows (19)
- # clj-yaml (2)
- # cljs-dev (39)
- # clojure (52)
- # clojure-czech (2)
- # clojure-dev (11)
- # clojure-europe (28)
- # clojure-hamburg (10)
- # clojure-hungary (3)
- # clojure-nl (1)
- # clojure-norway (59)
- # clojure-uk (5)
- # clojured (2)
- # clojurescript (33)
- # conjure (2)
- # datahike (1)
- # datomic (5)
- # defnpodcast (5)
- # emacs (18)
- # figwheel (2)
- # funcool (6)
- # graphql (1)
- # hyperfiddle (11)
- # jobs (3)
- # joyride (13)
- # malli (6)
- # music (4)
- # off-topic (45)
- # polylith (11)
- # practicalli (3)
- # rdf (3)
- # releases (1)
- # scittle (8)
- # shadow-cljs (13)
- # specter (2)
- # squint (8)
- # testing (6)
- # tools-deps (21)
- # xtdb (2)
I'm writing up a Discussion about https://clojurians.slack.com/archives/C03S1KBA2/p1683142572115519 and want to make sure I'm not missing a setting which already does what I want.
In the Clojure cli, a form like (let [x])
produces a short, informative message and hides the stacktrace. In CIDER 1.7 on my machine, cider-eval-last-sexp
(meaning, from a namespace buffer, not in the REPL buffer) the same form produces a pretty substantial and complex stacktrace with the root cause pretty well obscured.
Does CIDER currently provide a way for this error to surface nicely (that is, more like the CLI)? I'd still want an option to drill down to the full stacktrace, of course.
I started a discussion https://github.com/clojure-emacs/cider/discussions/3338
I use the setting (setq cider-show-error-buffer nil)
which shows the error message as an overlay at the end of the form being evaluated - the vast majority of the time I find this a much better user experience, and can always bring up the stacktrace buffer with cider-selector
if needed.
I started a discussion https://github.com/clojure-emacs/cider/discussions/3338