2:12:13lagashAnd I was meaning more, that the parser and the writer were integrated together, versus having two libraries, one for parsing, the other writing / generating
2:47:50phantomicsThat would be a good design choice for your library, making it integrated like that, but I don't know of any tool that makes that particularly easy, I expect you'd need to built it from scratch with a bunch of (format) calls
7:25:15beachcontrapunctus: scymtym worked on a parser for the dpANS TeX source, and he is able to produce nice HTML and also a format for a CLIM-based browswer.
7:25:34beachI think phoe declared that the UltraSpec way was not feasible.
8:20:41jmesI have an unorthodox directory where I need CFFI to look for .so files, how do I tell CL to look there?
8:44:42jmesI found out cffi:load-foreign-library has a :search-path keyword for this. But it's called from elsewhere, so never mind me.
11:55:41contrapunctusI'm trying to install cl-inotify, and I get this condition - https://paste.rs/Jkh I've tried installing libinotifytools0-dev, and restarting the Lisp process.
12:34:59jackdanielcontrapunctus: do you have c compiler?