Clojurians Log v2

For big outputs, it is optimal to use CIDER inspector, i.e. cider-inspect-last-exp. Would that serve your usecase better?

It could but it might need some tweaking in this case. Being able to integrate cider with https://github.com/techascent/tech.ml.dataset would be incredible.

There’s a function you can call on a dataset to convert it to a vector of maps (where each map is a row in the dataset). The cider inspect handles collections of maps nicely. Maybe it’s possible to have the inspector call that function before it tries to inspect a dataset?

For anyone else with the same issue, cider-pprint-eval-last-sexp is an alternative

https://clojuredocs.org/clojure.datafy/datafy exists precisely for this purpose. If tech.ml.dataset implents the datafy protocol, then it will automatically integrate with cider-inspector and other similar tools.

Two functions you may be interested in: https://techascent.github.io/tech.ml.dataset/tech.v3.dataset.print.html#var-print-range print range lets you set the number of lines which print --- There's also this one: https://techascent.github.io/tech.ml.dataset/tech.v3.dataset.html#var-print-all Which conveniently sets the metadata on a dataset to print all rows