Clojurians Log v2
cider 2026-08-02
Hi, I'd argue that the print-out of the jack-in command in the MOTD (removed in https://github.com/clojure-emacs/cider/pull/3984) is actually useful enough to be preserved. Especially given how messy the dependency resolution in tools.deps is sometimes, for me it is quite often vital to see what aliases have been used and what dependencies did CIDER itself inject.
It is especially true when CIDER outputs version mismatch warnings to your face in bold red, but then demands an extra action of , startup to figure out why the version did mismatch. By the way, to learn about this command I had to go into the changelog, it is not easily discoverable.
I would prefer to have an option to re-enable this on-demand, or maybe even revert the change if enough people agree. What do you think?
I'd like to have this as a customisation option, for convenience. That information feels like an anchor for me, and I felt its absence too, especially as I jump between different projects regularly.
I really like how clean it looks now, though I agree some of the printed information was occasionally useful. I would be in favor of a middle ground that prints a bit more than it does now, but probably less than it did before, carefully presenting the most useful information 👍
I agree. The informational block - bindings, help, etc. - wasn't useful too me, and it never changed. But the jack in command depends on the project and configuration, so I'm used to have it at hand.
i originally put it there to make it remove the mystery and reconnect it back to the normal way of running a process. Also lets you easily copy it and then run it in your own terminal and cider connect to it. I like demystifying the tools.
I'll think about this. I removed it mostly because it's in the Emacs message log already and I thought for newcomers it probably didn't mean much, and others could figure out how to find this.
I get it's useful information, but probably something you'd only summon on demand in most cases.
I actually forgot that it's in the message log too. It gets overwritten fast by the following messages.
And with figuring out, like I've said above, it's not easy to figure out. I had to learn about cider-repl-describe-startup from the changelog.
Related note, I had (have) configured (setq cider-repl-display-help-banner nil), which I like because it removes a bit of noise.
I think, for me, the optimal initial output would be something like:
;; Java 21.0.11, Clojure 1.12.4
;; CIDER 2.1.0-snapshot (package: 20260729.1056), nREPL 1.7.0
;; Starting server via /usr/local/bin/clojure -Sdeps {:deps {nrepl/nrepl {:mvn/version "1.7.0"} cider/cider-nrepl {:mvn/version "0.62.2"}} :aliases {:cider/nrepl {:main-opts ["-m" "nrepl.cmdline" "--middleware" "[cider.nrepl/cider-middleware]"]}}} -M:cider-defaults:cider/nrepl
;; Connected to nREPL server - wonder if there’s a way to fold the message. A clean startup does look nice, not gonna lie. It’d be neat if that information could be there when you want it (infrequently) and not take so much cognitive space when you don’t. Without having to restart with an option to see it. that’s a bummer. Maybe shoving this in the nrepl log buffer? capturing it in some other buffer for you?
As mention about typing ,startup shows it if needed, but perhaps that's not very obvious.
(and there's also M-x cider-repl-describe-startup)
The info is also in *messages* in my setup - perhaps just a pointer there would suffice. Lots of good ideas in this thread, you all are great. simple_smile 🙇