Clojurians Log v2

I haven't seen a lot of people using tap> yet

in the context of rebl and debugging, it can be handy

What does prepl make use of tap> for? Tap> is a core fn now. So it's more a question of should joker support tap> from core no?

whatever you tap> will show up on the prepl in an "unsolicited" manner -- it just suddenly shows up

Oh, I see. So prepl is always listening for taps and will print them out?

at any rate, for prepl-using purposes, i wonder how much use tap> is

that's how it looks to me

in the context of rebl, whatever you tap> will show up in the tap tab, after tap>ing multiple times, you can click "browse" and all of the accumulated tap> content is then made available for inspection in the main rebl ui

That sounds awesome. Might make my top 5 reasons to add multithreading to Joker! 😉

not quite sure what you are referring to, but for rebl to work, iiuc, it must be in the same process that a clj project is running in -- at least at the moment. i think there is some thought being given to things working over the wire (e.g. punk), but these things are even more early stage iiuc.

(i did succeed in converting emacs-lisp data structures to analogous clojure data structures and sending to rebl as well as punk though)

I mean, a prepl that doesn't print tapped value still seems useful

As I understand, prepl is just a socket repl that takes and returns EDN

Which makes it easier to use then a plain old socket repl

It seems it also has this tap> feature, but logically it seems it could still function without it

Unless a prepl client was relying on tap> to print info to the repl. Like say the client when you eval something did a tap> or if an exception was thrown it did a tap> to display it, etc.

yes, prepl without tap> seems plenty useful -- for tooling, it's much easier to parse the output (all maps). Olical's conjure is built using prepl.

return values and out and err are not all mixed together