Clojurians Log v2

Not really. It could be something needs fixing in VS Code itself.

I think it’s there, but we don’t print it because the command is “print stacktrace”. We can add a command for printing the data. I’ve never missed it myself because I just grab it from *ex if I need it.

There’s some specific situations in which the exception doesn’t get assigned to *ex, like when the exception occurs in a test run via a Calva command

Nobody is working on it, but there is no reason to not surface ex-data in some way.

It may be something to confirm with an experiment: if the ex-data is there in the nrepl response for these specific situations.

Good point. I’ve also noticed that calva renders a “show stack trace” button in those cases but clicking it doesn’t do anything

Ah. You could file an issue about that observation.

Will do

https://github.com/BetterThanTomorrow/calva/issues/2900

nice round number 🙂

Could you point me to where it would go in the code, and to where printing Clojure data structures happens? I might take a crack at if

I think it could make sense to first look if this should be a feature of the output window. @brandon.ringe ?

Seems like it would be fairly easy to do. I don't know the details but I'm guessing either that ex-data is available in an nrepl message and Calva just isn't printing it, or we need to make the code retrieve it if it exists somehow, then print it.