Fork me on GitHub
#cider
<
2022-01-14
>
Nom Nom Mousse06:01:54

Just found out about the debugger. What a marvel CIDER is โค๏ธ

Nom Nom Mousse06:01:12

I have a web app running, started from within the CIDER REPL. I have added breakpoints to a part of the backend code, evaluated the buffer, and then invoked the function again indirectly (click front-end button which sends a request to the backend). But CIDER does not break at the breakpoint. Should what I am trying to do be possible? I.e. adding breakpoints to a live app?

bozhidar07:01:50

@endrebak It should work. There was a bug in older versions that messed up the debugger over http, but we addressed it last year https://github.com/clojure-emacs/cider-nrepl/issues/689

๐Ÿ™ 1
Dimitar Uzunov14:01:13

Hi is there a way to display the history of the return values of evaluated forms (like you do with C-c C-c)?

Dimitar Uzunov14:01:48

I see there is M-x cider-repl-history but it is empty, mostly likely because I donโ€™t type in the repl window

dpsutton14:01:46

i think this is what the repl is good for. I always send forms to the repl so i have a history of it

Dimitar Uzunov14:01:52

I usually use C-c C-p to print to another window when I know I want to read the output, but sometimes when eval-ing forms I want to take a second look

practicalli-john21:01:12

@dimitar.ouzounoff to navigate through the history of evaluated form results, I suggest using Portal - https://github.com/djblue/portal which can be used as a tap> source and keeps a history of the results sent to portal. A very simplistic approach is to evaluate results to a comment, cider-eval-defun-to-comment in the source code buffer and keep all the comments. Each new evaluation adds a comment The Cider repl history only keeps a the history of forms and not their results.

๐Ÿ‘ 1