For what it's worth, I'd prefer that the markdown documentation die a natural death in favor of the texinfo documentation.

The markdown documentation requires a complex toolchain (cl-markdown + many dependencies) that the average ASDF user cannot be expected to have. It also works poorly when you are off the web.

By comparison, texinfo requires what almost every lisp user will have, a standard gnu-based environment, with makeinfo, and generates output forms (pdf and info) that can readily be used off line.

Cheers, Robert

On 1/24/10 Jan 24 -12:45 PM, Daniel Herring wrote:

On Sun, 24 Jan 2010, Robert Goldman wrote:

...

For what it's worth, I'd prefer that the markdown documentation die a natural death in favor of the texinfo documentation.

I'm just trying to fix a common markdown error in all the packages I use. Patching or removal: both fix the problem. If removal will take a while, I'd appreciate this patch in the meantime.

If ASDF decides to remove the markdown, please check that all useful info has been merged to texinfo, and update the website and README.

I have already done the merge back to texinfo.

I don't know how to manage the website or README, though; I will leave that to someone else.

It might be nice if the implementations that ship with ASDF were to compile the manual into (at least) pdf or html, so that their users get easy access.

On a related topic: The manual badly needs an extension of the discussion on the object model and how to make your own operations and components. The protocol isn't as well documented as one might wish; I find myself doing more trial-and-error programming than I'd like here.

best, r