Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loops debugging #7

Open
wkok opened this issue Dec 11, 2023 · 1 comment
Open

Loops debugging #7

wkok opened this issue Dec 11, 2023 · 1 comment

Comments

@wkok
Copy link

wkok commented Dec 11, 2023

Is there a way currently to support loops debugging?

Like in the Flowstorm UI, where we can select a value of a local from some list and have it jump to that frame?

Thanks for this emacs package it rocks!

@jpmonettas
Copy link
Member

This feature isn't implemented on cider-storm yet, but shouldn't be hard. The only tricky part would be thinking about performance of different solutions.

One option could be :

  • On the Clojure side, extend the middleware with an OP like get-all-expressions-vals-for-frame-coord that will receive the current flow-id, thread-id and fn-call-idx and just call frame-data with {:include-exprs? true}. Then returns a list all the timeline entires with the requested coordinate pprinted-val and idx.
  • On Emacs side, create a elisp command like cider-storm-select-current-coord-expression which will retrieve all possible timeline entries using the middleware defined above and show a completing read menu to choose what to jump to, and then jump to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants