20:13:06White_Flamerodriga: usually, the macro-based customization of CL is focused around creating the proper abstractions for your codebase, which just gives a few enhancements and interacts well with CL in a very readable way, not it's own completely separate languages
20:27:47jackdanielclearly since there are multiple appenders it uses multiple streams
20:31:55Josh_2Yes, basically the old functionality just locally bound *standard-output* so that I could grab the output and send it over a socket, but then I swapped my logging system to log4cl and this obviously broke
20:36:23mfianoThis isn't an answer, but perhaps try verbose.
23:23:10jasomIs there a library that makes a non-seekable stream (somewhat) seekable by adding buffering on top? I'm thinking something that guarantees always allowing seeking back N elements (up to the beginning, where N >> 1 and is possibly configurable)
23:28:16mfianoA Gray stream wrapper for that would be only a couple lines of code not even worth a library
3:30:55jasommfiano: it's not the number of lines of code, it's how long it takes to write the lines of code. I've written something similar before and I had some subtle bugs with my first implementation.