Nikolaos Chatzikonstantinou <[email protected]> writes: > On Sun, Oct 5, 2025, 7:38 PM Tomas Volf <[email protected]> wrote: > >> Nikolaos Chatzikonstantinou <[email protected]> writes: >> >> > Hello list, >> > >> > I've compiled a list of Guile skeleton projects with Autotools >> > (autoconf, automake) here: >> > <https://codeberg.org/annoyingusername/guile-project-skeletons-autotools >> >. >> > Hopefully this will be useful to others. I tried to cover all the >> > cases that I could come up with. >> >> Looks interesting. I should probably find the time to publish my own >> project blueprint repository. From my experience, the most annoying >> part to get at least semi-right are dependency tracking and >> documentation generation, so it would be nice if that was covered. > > > Which part of documentation generation? Im currently writing a Guile > library that i will publish soon and I will also add an example project > that shows how to get texinfo docs into HTML in codeberg pages with their > CI. (If that is what you meant.)
Ah, my bad, I should have been clearer. I have meant generating (part of) the texi file from the scheme source code. In both Guix and Guile, there is a problem that useful procedures exist, are exported, but they are not mentioned in the manual, making it hard to discover them. In my projects I have "solved" this problem by generating part of the manual based on public bindings of the modules. See this[0] section. Not all variables have associated documentation string, true, but at least their existence is documented. Dunno, it is possible this is just matter of personal preference and other people do not find it useful. ^_^ Tomas 0: https://files.wolfsden.cz/manuals/guile-wolfsden/guile-wolfsden-0.0.7.html#Auto_002dgenerated-documentation -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
