May 2006 - cl-markdown-devel@common-lisp.net

[cl-markdown-devel] Re: Problem while compiling metatilities
by Gary King 23 May '06

23 May '06

Hi Lars, This bug has been corrected. My apologies. On May 23, 2006, at 5:20 PM, Lars Rune Nøstdal wrote: > Hello there :) > I get this while compiling metatilities (dependency of cl-markdown): > > The file "/home/lars/programming/lisp/metatilities/dev/api.lisp" > does not exist. > > The file doesn't seem to exist in the darcs-repo either. > > -- > Mvh, > Lars Rune Nøstdal > http://lars.nostdal.org/ -- Gary Warren King metabang.com http://www.metabang.com/ (413) 210 7511 gwking on #lisp (occasionally)

1 0

[cl-markdown-devel] CL-Markdown update
by Gary King 22 May '06

22 May '06

Apologies if you've already read this on Planet Lisp... I've removed CL-Markdown's dependency on LML2 (though CL-Markdown- Test still uses it to generate the comparison reports). I've also fixed several small tickets. The most important one probably being the correct handling of line breaks with <pre>s sections. I also changed the signature of the markdown form. The new one looks like: > Convert source into a markdown document object and optionally > render it to stream using format. Source can be either a string or > a pathname or a stream. Stream is like the stream argument in > format; it can be a pathname or t (short for *standard-output*) or > nil (which will place the output into a string). Format can > be :html or :none. In the latter case, no output will be generated. > > The markdown command returns (as multiple values) the generated > document object and any return value from the rendering (e.g., the > string produced when the stream is nil). I hope that's clear. It makes it easy to go from strings or files to strings or files in any supported format (i.e., in HTML <Smile>). There is still some distance to go before the basics are complete but things are starting to look pretty good. -- Gary Warren King metabang.com http://www.metabang.com/ (413) 210 7511 gwking on #lisp (occasionally)

1 0

[cl-markdown-devel] tickets 15 and 16
by Gary King 14 May '06

14 May '06

Auuugh. My apologies. I'll let you know once I resolve both the missing dependencies and the SBCL faults. -- Gary Warren King metabang.com http://www.metabang.com/ (413) 210 7511 gwking on #lisp (occasionally)

1 0

[cl-markdown-devel] Comparison tests have been updated and improved
by Gary King 11 May '06

11 May '06

The tests now show when the comparison exactly matches the output of Markdown and the number and type of differences are reported when they don't match. I've also fixed ticket #8 so that CL-Markdown correctly gets ***strong and em***. -- Gary Warren King metabang.com http://www.metabang.com/ (413) 210 7511 gwking on #lisp (occasionally)

1 0

[cl-markdown-devel] Re: cl-markdown
by Gary King 10 May '06

10 May '06

Hi Clemens, This sort of hack is definitely possible though there isn't anything in place right now. I'd suggest adding a ticket via the trac interface (http://trac.common-lisp.net/cl-markdown/newticket) CL-Markdown runs in two "phases". The first does the parsing and the second the generation (not too surprising!). The parsing API is pretty ugly right now and should be improved. I'll keep your desires in mind when I get to that step. thanks, On May 9, 2006, at 4:27 PM, Clemens Heitzinger wrote: > Hello, I just read your announcement. > > I'd like to use it to write some pages. My gripe with markdown.pl > is that I cannot include the html, head, and body tags like in the > example below. (At least I couldn't figure it out.) I thought I > could hack cl-markdown to include headers and footers in the > pages... Everything before and after the two comments would go > verbatim into the output file. Would that be feasible? > > —Clemens > > > > <html> > <head> > <title>Research</title> > <link rel="stylesheet" type="text/css" href="homepage.css"> > </head> > <body> >  > > # Header 1 > > Markdown text goes here. > >  > </body> > </html> > > -- Gary Warren King metabang.com http://www.metabang.com/ (413) 210 7511 gwking on #lisp (occasionally)

1 0