>>106564900
>Btw, anyone knows of good resources to learn the repl? I've heard people saying you can do profiling and stepping etc, but I'm a lowly 'using format to print shit and debug' kinda guy.
Are you using sly or slime to interact with your CL REPL? If so, every result is clickable and brings up the inspector which lets you inspect data. This should reduce the amount of manual printing you have to do.

Sly configuration I recommend:
(use-package sly
:ensure t
:config
(let ((patterns '(("\\*sly-mrepl"
(display-buffer-in-side-window)
(side . bottom)
(slot . 0)
(window-height . 18))
("\\*sly-db"
(display-buffer-in-side-window)
(side . bottom)
(slot . 1))
("\\*sly-inspector"
(display-buffer-in-side-window)
(side . right)
(slot . 1)
(window-width . 80))
("\\*sly-description"
(display-buffer-in-side-window)
(side . right)
(slot . 0)
(window-width . 80)))))
(cl-loop for p in patterns
do (add-to-list 'display-buffer-alist p)))
(setopt inferior-lisp-program "/usr/bin/sbcl")
(setopt org-babel-lisp-eval-fn #'sly-eval))

Be sure to set inferior-lisp-program to a value that's appropriate for your system. Any time you want access to a CL REPL, you can `M-x sly`. To shut down a REPL, use `M-x sly-quit-lisp` or ,q .