vim

Chase 2025-11-20T18:10:35.087239Z

Wanted to also ask this conjure question here as I don't think the actual #conjure channel is too active

Chase 2025-12-05T21:13:24.316989Z

Coming back to this actually just using clojure.pprint/pprint manually on the data is showing correctly now in the conjure repl buffer. Maybe it's because I took the Thanksgiving break to update my whole dev workflow or something because that wasn't working before. shrug

❤️ 1
Chase 2025-12-05T21:32:15.592319Z

I'll still look for a way to make that the default so I don't have to manually call it on the data I want pprinted. Because if I don't use it manually I still get the big long single line output of large data

Chase 2025-12-05T21:49:04.988489Z

The weird thing about it is I use the cider nrepl middleware (for both nvim and emacs) and if I understand the docs correctly it defaults to using clojure.pprint/pprint already...

2025-11-20T20:07:17.969149Z

For larger values I find it useful to send them to Portal, and drill into and explore graphically. I use it like:

{
    no_key,
    desc = "Clojure: Open Portal",
    function()
      require("conjure.eval").command([[
    (do
      (ns dev)
      (def portal ((requiring-resolve 'portal.api/open)))
      (add-tap (requiring-resolve 'portal.api/submit)))
  ]])
    end,
  },
  { "<localleader>et", "<cmd>:ConjureEval (tap> *1)<cr>", desc = "Eval: Tap last value" },

Chase 2025-11-20T22:25:16.900269Z

I appreciate this answer as after some discussions at the Conj I was thinking I need to explore Portal more. This is another good signal to do so

Chase 2025-11-20T22:25:38.153719Z

This workflow works for test results?