cl-markdown-devel

cl-markdown-devel@common-lisp.net

49 discussions

[cl-markdown-devel] Re: compile error in cl-markdown/Lispworks
by Gary King 24 Oct '07

24 Oct '07

(cc'd to list) Hi Juergen, Thanks for pointing this out. I just released 0.9.0 today which includes this fix. On Oct 18, 2007, at 2:22 PM, Juergen Gmeiner wrote: > Hi, > > there is a compile time error in dev/docs.lisp as installed via > asdf-install today. > > The method find-documentation references "mop:generic-function- > methods" ... this package does not exist that way on lispworks. > i changed it to "mopu:generic-function-methods" and it seems to work. > > regards, > Juergen > -- > Juergen Gmeiner <gj(a)gjdv.at> +43-676-4163598 > > > > -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[cl-markdown-devel] trivial patch
by Henrik Hjelte 28 Sep '07

28 Sep '07

Thanks for a great library. Being a newbie, my first patch is only one letter long, a typo changing mop to mopu. Funny I made a typo as well in the darcs description... /Henrik Hjelte

1 0

[cl-markdown-devel] (no subject)
by Luke J Crook 20 Jul '07

20 Jul '07

Should I use (find-system 'cl-markdown) to detect if CL-MARKDOWN is loaded? - Luke

2 1

Re: [cl-markdown-devel] Documentation?
by Gary King 27 Jun '07

27 Jun '07

Hi Andreas, Documentation is one of the things sorely lacking from CL-Markdown. For now, here is the docstring of the markdown function: > "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\)." So, for example, > markdown> (markdown " > ### Title > > Some text > > * a list > * with sublists > * and so on > * and so on > > More text" :stream nil) > #<document @ #x11c93f92> > "<h3>Title > </h3> > <p>Some text > </p><ul><li>a list > <ul><li>with sublists > </li><li>and so on > </li></ul></li><li>and so on > </li></ul><p>More text > </p>" > markdown> I do hope to be able to stop developing a manual in the relatively near future... Please let me know if you have any more questions, -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

2 2

[cl-markdown-devel] HTML generation questions using cl-markdown (fwd)
by Luke J Crook 30 Mar '07

30 Mar '07

I sent this to the announce list by mistake. - Luke ---------- Forwarded message ---------- From: Luke J Crook <luke(a)balooga.com> To: cl-markdown-announce(a)common-lisp.net Subject: HTML generation questions using cl-markdown Date: Thu, 22 Mar 2007 15:20:47 -0400 I'm unsure if these two issues are a limitation in the Markdown syntax or a bug in CL-MARKDOWN. 1) I'm getting an error when I have the following in CL-MARDOWN: [*DEFAULT-SURFACE*](#*default-surface*) No applicable methods for #<STANDARD-GENERIC-FUNCTION CL-MARKDOWN::RENDER-TO-HTML 221D7552> with args (CL-MARKDOWN::EMPHASIS NIL) 2) CL-MARKDOWN doesn't seem to render quotes in code (indented 4 spaces). For example: \(DRAW-STRING-SHADED-* \"Hello World!\" 0 0 F-COLOR B-COLOR :SURFACE A-SURFACE\)" Will give the following: (DRAW-STRING-SHADED-* "Hello World!" 0 0 F-COLOR B-COLOR :SURFACE A-SURFACE) Thanks, - Luke

2 2

[cl-markdown-devel] hard returns problem returns
by Hans Halvorson 12 Mar '07

12 Mar '07

Some problems with formatting bullet lists with hard returns have reemerged in version 0.8.7. Here is a sample: (markdown "* A list element with a hard return. * A second list element with a hard return, for which we add some superfluous material" :stream t) ==> <ul>A list element with a </ul>hard return. <ul>A second list element with a hard return, for which we add </ul><p>some superfluous material </p> Best wishes, Hans

2 2

[cl-markdown-devel] Announcing: CL-Markdown 0.8.7
by Gary King 04 Mar '07

04 Mar '07

Thanks to more helpful bug reports from Hans Halvorson and others [CL- Markdown][] is now at 0.8.7. The changes modify block structure detection in the parser to be more in line with the actual Markdown syntax, implement the two #\Spaces at the end of a line means `<br / >`, and new HTML rendering to get the output closer to fine. CL-Markdown deviates from Markdown in that it continues to parse Markdown syntax even within block tags. I view this as a bug, not a feature. See [Pandoc][] and [maruku][] for additional riffs on this theme. [maruku]: http://rubyforge.org/projects/maruku/ [Pandoc]: http://sophos.berkeley.edu/macfarlane/pandoc/README.html [CL-Markdown]: http://common-lisp.net/project/cl-markdown/ -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[cl-markdown-devel] div tags
by Hans Halvorson 28 Feb '07

28 Feb '07

cl-markdown does not yet treat <div> tags in the special way that perl-markdown treats them; instead cl-markdown wraps <div> tags in <p> tags. Here is an example input string: input string (9 lines total): ============================= <div class="header"> Header text </div> # Heading Some text Here are the respective output strings: cl-markdown output: =================== <p><div class="header"> </p><p>Header text </p><p></div> </p><h1>Heading </h1> <p>Some text </p> perl-markdown output: =====================x <div class="header"> Header text </div> <h1>Heading</h1> <p>Some text</p> See the description of how perl-markdown treats div tags: http://daringfireball.net/projects/markdown/syntax#html Thanks, Hans

3 4

[cl-markdown-devel] manual line breaking
by Hans Halvorson 27 Feb '07

27 Feb '07

In perl-markdown, a couple of whitespaces at the end of a line are rendered as a <br /> tag. It does not appear that cl-markdown has implemented this feature yet. For example, consider the following input text (note that there are two whitespaces at the end of "First line"): First line Second line Output from perl-markdown: ========================== <p>First line<br /> Second line</p> Output from cl-markdown: ======================== <p>First line Second line</p> Best wishes, Hans

1 0

[cl-markdown-devel] Re: feature request (user guide)
by Gary King 27 Feb '07

27 Feb '07

(cc'd to list -- hope you don't mind) Hi Hans, I'm glad you got them to work and I apologize that they are so _crufty_. I think what I'd like to do is make a macro that does some of the grudge work for you. I have vague hope that I'll do a first step along these lines this week). On Feb 26, 2007, at 4:22 AM, Hans Halvorson wrote: > Dear Gary, > > Thanks for writing the cl-markdown user guide --- it has been very > helpful for me. > > I have one request/suggestion for the user guide: > > When writing my own extensions, I was stymied for a while because I > was getting errors telling me that my function was being called with > the wrong number of arguments. For example, I defined the following > function to give the version number of a system: > > (defun version-number (systemname) > (asdf::component-version (asdf:find-system systemname))) > > If I put "{version-number cl-markdown}" in my document, I got a couple > of errors --- the first error told me that version-number was being > passed the wrong number of arguments. After looking at your examples, > I figured that I should define: > > (defun version-number-2 (phase systemname result) > (declare (ignore phase result)) > (asdf::component-version (asdf:find-system systemname)))) > > I then received an error that "(cl-markdown) isn't a valid system > name." So, I defined: > > (defun version-number-3 (phase systemname result) > (declare (ignore phase result)) > (version-number (car systemname))) > > and it worked. So, could you write something in the user guide > explaining the proper format for extension functions? > > Thanks, > Hans -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

cl-markdown-devel