declt
declt copied to clipboard
Reference manual generator for Common Lisp libraries
I've just pushed out some newly generated documentation, and there are a few things I'm not clear on. The HTML docs were generated with makeinfo, and the doc link is...
I am trying to generate documentation for a sub-system and declt is having trouble with the directory names. The use case is a plotting system, with multiple back-ends, so there...
Perhaps naming of the Conclusion node should be user configurable. For example one might wish this section to be named "Change Log". One way to do this would be to...
I see a state diagram of sorts at the [overview page](https://www.lrde.epita.fr/~didier/software/lisp/declt/user/Overview.html). How is this done?
Is there a way to call `declt:declt` and `makeinfo` from ASDF via some kind of doc-op? It would be nice to be able to automate the documentation of multiple systems...
I think the output of the declt manuals and user guide looks far better than what I get with 'out of the box' `makeinfo`. Can you recommend a style sheet...
I didn't know quite where in the lisp community to put this. Perhaps reddit/common-lisp at some point. I'm not assuming that you would do this work, nor am I suggesting...
A lot of the code I'm writing requires (well, should have) citations to the reference paper/implementation/etc. Pandoc can [automatically generate citations](https://pandoc.org/MANUAL.html#citations), and it would be nice if we could somehow...
Such code can be used with minor changes, to process case when license is not present: ``` (intern (string-upcase (asdf:system-license (asdf:find-system system-name))) "KEYWORD")) ```
Perhaps using [introspect-environment](https://github.com/Bike/introspect-environment)?