I found that sometimes ql:quickload just silently skips serious errors like:
;Compiler warnings for "home:common-lisp;mito-email-auth;src;models.lisp.newest" :
; In SEND-CODE: In the form ("Для входа на сайт [Skazorama.ru](~A), перейдите по [этой ссылке](~A)" URL URL), "Для входа на сайт [Skazorama.ru](~A), перейдите по [этой ссылке](~A)" is not a symbol or lambda expression.
(I forgot to import a macro into the package. This macro should transform the code into something useful).
But when I'm loading this library using asdf:load-system, an error pops up and is available for debugging.
How do you live with that behavior?
This is a problem with Quicklisp, and I don't know a good fix.
It happens because Quicklisp, by design, suppresses the loading output of the libraries it provides, and summarizes progress by printing .s. The idea is that these supporting libraries are settled infrastructure, and the output is unnecessary extra noise.
However, this is bad behavior when loading your own projects, which might be in flux, and for which verbose and informative messages are useful.
I have not yet come upon a system to show verbose output for your own projects and terse output for Quicklisp-provided projects. In the meantime, for my own purposes, I find that (ql:quickload "my-project" :verbose t) or setting *quickload-verbose* to true work as I need. If those options don't work for you, I'd be curious to know more about your configuration, e.g. what implementation and version is in play.