some unfortunate indenting..

I’d prefer to see these as a vertical column. This make it hard to see.

Although it is more compact, so I realize there’s a tradeoff..

ps I’m learning to use portal more, so maybe not crucial to solve?

The formatting for the terminal output is done using zprint, so we really could make it customizable.

Or we could go for Tonsky style formatting and skip making it customizable. I would lean towards this option.

Also, I’m super keen to hear what you think of the new inspector, so would love if you installed the latest VSIX build of that and took it for some spins.

I played with new inspector today. Looks neat. I like the value icons. My first impression is that i would want to see the last form auto expanded, on top, with maybe levels 2-n folded? I guess it depends. But im orobably thinking of it like normal results, not a backup drill-down explorerer it currently is. But to really use it a lot i wouldnt want to have to click and drill after every eval? All in all, the more results options the better! If the repl is our super power, taking the viz + interaction to the logical extensions just makes sense 👏

Thanks for having a look! The reason we don’t auto-expand is that it can take some time, depending on the size of the structure, and it locks the ui during. We could consider a configuration which enables auto-expansion, but maybe it is better that the user uses runCommands to string the evaluation and the expansion. But first we must enable the expansion via an exposed command, of course.

You shouldn’t need to downgrade Calva. The change was only about default dependencies. You can use whatever versions via the setting calva.jackInDependencyVersions:

"calva.jackInDependencyVersions": {    
    "nrepl": "1.1.1",
    "cider-nrepl": "0.47.1",
    "cider/piggieback": "0.5.3"
  } 

We could consider trying to detect Java 1.8 and use special jack-in deps then, or inform about the setting then.

This was a relative beginner and I wasn't about to try to navigate them through modifying their settings JSON to add that stuff on the fly, especially since neither they nor I knew the appropriate nrepl or cider-nrepl versions off the top of our heads. Downgrading Calva was the easiest solution for them now.

I think 2.0.436 was jacking in with nrepl 1.0.0 and cider-nrepl 0.28.5? No idea about piggieback (which they're not relying on). Is there a specific doc link I could send them with the correct older nrepl/cider-nrepl deps so they could make this change themselves without breaking anything?

You think the right versions:

diff --git a/package.json b/package.json
index 348e1b34..c06dba94 100644
--- a/package.json
+++ b/package.json
@@ -491,8 +491,8 @@
               }
             },
             "default": {
-              "nrepl": "1.0.0",
-              "cider-nrepl": "0.28.5",
+              "nrepl": "1.1.1",
+              "cider-nrepl": "0.47.1",
               "cider/piggieback": "0.5.3"
             }
           },

I added a note here now: https://calva.io/customizing-jack-in-and-connect/#jack-in-dependency-versions

Perfect! Thank you!

True, but using a different version for dev to prod can lead to mistakes -- accidentally using a 1.9-only function or having subtly different behavior -- and this was a relatively new developer, working on a large project with a lot of old dependencies that their teammates wouldn't want them to mess with in project.clj. I was shocked to see their project was still using Clojure 1.8 👀

I'd assume CI can catch such things. One can be very surgical with profiles e.g. add a :cider profile which by virtue of being decoupled to :dev , is guaranteed to not affect anything else.

then again, if Clojure 1.8 was in use perhaps CI would need some TLC in that particular project.