flowstorm / ciderstorm seems to fit the bill

Ah interesting I haven't used it before

With cider you can already trace functions but it depends on what you mean by tracing

Well I normally only need the value of a few vars not the whole function

Which I would print or tap or def

@U45T93RA6 how would you describe the maturity/usefulness of ciderstorm to flowstorm? I notice flowstorm seems to get the most dev attention, but I don't know if thats just because ciderstorm was much more easily "completed" :^)

@U0739PUFQ would know best how to answer that!

@U0482NW9KL1 so FlowStorm would be the thing recording in both cases, so the recording is going to be the same. Then for exploring your recordings (like stepping) you can use the FlowStorm UI or cider-storm which is a Emacs UI for the same thing. The difference is that cider-storm UI provides a small subset of all the features provided by the FlowStorm UI, but both can be used at the same time

personally I just use the FlowStorm UI, but if you prefer to be in Emacs as much as you can, you can use cider-storm to do some stepping in emacs and if you need more features just eval the :dbg keyword and you are going to have the FlowStorm UI to explore the same recordings

does it make sense?

much appreciated @U0739PUFQ, it does, I've used FlowStorm for a while now, and only recently came across Ciderstorm, but have yet to give it a try as I figured FS's UI was more fully featured :^) 👍

yeah, cider-storm so far is just the the quickbox jump + the stepper in Emacs

but even the stepper is less powerful because you can't click around, add prints, use the context menu jumps, no power stepping