- cl-markdown-devel@common-lisp.net - mailman3.common-lisp.net

[cl-markdown-devel] new version : 0.8.0
by Gary King 06 Oct '06

06 Oct '06

The main addition in this version is support for {include pathname}. Included files are merged directly into the stream of the source currently being processed and are processed along with them. In other words, if we have file1.md and file2.md > ;; file1.md > {include file2.md} > > this is the body > ;;file2.md > ## This is the title then the output of (markdown "file1.md") would be > <h2>This is the title</h2> > <p>this is the body</p> Their are other bug fixes and minor improvements (and probably some new bug additions as well). share peace, -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[cl-markdown-devel] minor updates to cl-markdown
by Gary King 13 Jul '06

13 Jul '06

I've made several small tweaks to CL-Markdown in an effort to bring it a bit closer to its Perl cousin. In particular: * I finally began to add to support for escaped characters (e.g., you can now say \*hello\* to output *hello*). * Corrected a few edge cases and missing bits of support for links * Many some very small improvements in the handling of Markdown coding with code blocks (it's not complete, but every step is a step). As usual, CL-Markdown has a host of dependencies. You may want to try System-check to see what needs to be updated. -- Gary Warren King metabang.com [http://www.metabang.com/] (413) 885 9127 * (206) 338-4052 [Fax] gwking on #lisp (occasionally)

1 0

Re: [cl-markdown-devel] #. compile problem
by Gary King 12 Jun '06

12 Jun '06

Hi Ties, I've looked into this a little more and here is what I think is happening: CL-Markdown uses my containers library (CL-Containers) and, in particular, the iterator constructs. These let me create an iterator and use it without caring about where the data originates because the iterator is supposed to abstract all of that out. So the call in chunk-source can look like: > (with-iterator (i source :treat-contents-as :lines :skip-empty- > chunks? nil) > (iterate-elements > i > (lambda (line) > (chunk-line line)))) where source can be a string or a pathname. The with-iterator macro eventually turns into a call to make-iterator and make-iterator uses the arguments it is supplied to construct the appropriate class and instantiate it. in particular, if source is a pathname, the iterator will be of type 'file-line-iterator; if source is a string, you'll get a 'line-iterator. The line-iterator is a subclass of delimited iterator and uses #\linefeed, #\newline (and now #\return) to find lines. On OS X, this code > (list (char-code #\linefeed) (char-code #\newline) (char-code # > \return)) return various things in various Lisps: > (MCL) ==> 10 13 13 > (SBCL 0.9.11) ==> 10 10 13 > (OpenMCL) ==> 10 10 13 So if one of your strings had switched to #\return's instead of # \linefeed or #\newlines, then this is probably what caused the problem. I'm adding #\return to the list of delimiters for the line- iterator so that should correct this problem. Note that the file-line-iterator uses read-line to suck in each line. This means that the changing the delimiter won't have any effect on files. It also means that the line ending in files will be significant to CL-Markdown (i.e., CL-Markdown won't work correctly if read-line doesn't read lines <smile>). HTH, please keep me informed as to any more trials and tribulations you encounter (and successes too!) On Jun 9, 2006, at 3:59 PM, Ties Stuij wrote: > Eureka! > i got it. > >> So are you saying that >> >> ? (markdown "..." :stream t) >> >> works but >> >> ? (markdown "..." :stream "/my/file/name/here") >> >> fails? > > No i store two strings in elephant class slots: the markdown text and > the output of the markdown. Since elephant only references slots you > ask for, this seemed to me to be the most efficient way to use it. If > you want to update the text you can edit it in place through a form > (we're talking browsers here). > > Anyway, it turns out that get?/post?/the browser?/ucw? saves > line-jumps as returns in stead of newlines. Something a newbie like me > doesn't think about so fast. I solved it in my app by regexp-replacing > through the string. I was gonna supply a patch but i noticed your code > decides on a low (container) level if the text you want to process is > a string or whatever, so i don't really know what is the preferred > route. > > Btw, while on my bughunt i installed through asdf-install and noticed > it installed a couple of dependencies that were not needed with the > darcs markdown, eg trivial shell, lml2, lift, cl-html-diff and > cl-difflib. You probably knew this and it is no biggie but you never > know. > > Anyway, thanks for the help, > > Greets, > Ties -- Gary Warren King metabang.com http://www.metabang.com/ (413) 210 7511 gwking on #lisp (occasionally)

1 0

[cl-markdown-devel] #. compile problem
by Ties Stuij 09 Jun '06

09 Jun '06

He Gary, Sbcl is not totally happy with cl-markdown. In line-is-link-label-p it won't fasl-ize #.(ppcre:create-scanner '(:sequence link-label)) eg: ; file: /home/zeno/lisp/lib/cl-markdown/dev/markdown.lisp ; in: DEFUN LINE-IS-LINK-LABEL-P ; (CL-PPCRE:SCAN #<CLOSURE # {D461E9D}> CL-MARKDOWN::LINE) ; --> CL-PPCRE:SCAN LOAD-TIME-VALUE SB-KERNEL:MAKE-VALUE-CELL ; --> CL-PPCRE:CREATE-SCANNER ; ==> ; #<CLOSURE (LAMBDA #) {D461E9D}> ; ; caught ERROR: ; Objects of type FUNCTION can't be dumped into fasl files. the form should work fine without reading it in advance, or ..? btw, i just got cl-markdown hooked up in the web-app i'm working on. It functions quite nicely. A whole lot better than the nl2br methodology, thanks! Greets, Ties

2 6

[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