12:52:10Xachto make it easier to find quicklisp dist-building errors, i've made some filtering that highlights only the fatal ERROR and WARNING parts from the build log.
12:52:42Xachi wonder if it would be useful to make that easily runnable by anyone so they can quickly get to the important output
13:10:31drlWhy does (format t "~%~%~%~%~%~%~%~%~%~%~a~%~%~a: " "PRAYER Ver. 1.1 MAIN MENU" "<A>dd-records <E>dit-records <P>ray <R>eports <Enter>-exit") print both strings at the repl, but after using save-lisp-and die to make a stand-alone executable only the first string prints?
13:41:11_deathinteresting that FORMAT lacks a directive to clear/force/finish output.. in my OUT macro I added an (:fo [:wait boolean]) operator (no clear operator though.. never used it)
13:43:04_deathI guess in FORMAT it would've been a "waste of a character" or something.. since it's not often you want to force/finish in the middle of output
14:21:19aneXach: what sort of build tests are run for quicklisp distributions? how are cyclic dependencies or dependencies towards other QL packages handled for a single system?
14:25:52phoeane: cyclic dependencies are detected on ASDF level, Quicklisp has nothing to do with that