The Common Lisp Cookbook – Debugging

It’s been already a little more than a year that I began my Lisp journey. I made quaterly news digests, mainly from reddit’s feed: Q1 2018 - Q2 2018 - Q3 2018 - Q4 2018 Time has come for a yearly overview ! What happened in the Common Lisp world ? Are there (or groundbreaking promising useful fun) projects, articles, discussions, tutorials ?No need to say, I won’t reference everything we find in the quaterly posts, which don’t list all new projects appearing on Quicklisp (we can find these in the monthly Quicklisp releases) or Github.

Stating the obvious: using the REPL to live-reload a running website - vindarel/demo-web-live-reload

Stating the obvious: using the REPL to live-reload a running website - vindarel/demo-web-live-reload

A web template with Hunchentoot, Easy-routes, Djula templates, Bulma CSS. - vindarel/lisp-web-template-productlist

You are doing god’s work on a time-intensive computation, but your final step errors out :S Are you doomed to start everything from zero, and wait again for this long process? No! Find out.I show this with Emacs and Slime, then with the Lem editor (ready-to-use for CL, works with many more languages thanks to its LSP client).(This video is so cool :D Sound on) We use the built-in Common Lisp interactive debugger that lets us restart one precise frame from the call stack.

We all know that we can start a web server in the REPL and develop a web app as interactively as any other app, we know how to connect to a remote Lisp image by starting a Swank server and how to interact with it from our favorite editor on our machine, we know we can build a self-contained binary of the web app and simply run it, but one thing I had not realized, despite being the basics, is that by starting the web app with sbcl --load app.

Under the hood of FireDBG