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

[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

[cl-markdown-devel] Re: cl-markdown (hangs head in shame)
by Gary King 21 Feb '07

21 Feb '07

(added the mailing list) Hi Luke, No apologies necessary; I'm sorry that this is taking so much effort on your part and appreciate that you are sticking with it. I'll look into the problem you are seeing with defsystem- compatibility. FWIW, I just successfully loaded the bundled version (currently at http://www.metabang.com/resources/cl-markdown- bundle.tar.gz) in the LispWorks personal edition. So if you haven't tried that yet, it might be worth doing so. thanks again, On Feb 20, 2007, at 11:34 PM, Luke J Crook wrote: > Hi Gary, > I must appologize for not trying cl-markdown after you made your > fixes last week. I know it sucks when I make changes in lispbuilder > per user feedback and then don't receive further feedback. > Anyway, I tried cl-markdown today with the latest versions of > everything using darcs pull. > The bad news is that cl-markdown still fails. The error returned in > the SLIME buffer not make much sense, however the error in the > Lipsworks buffer seems to shed more light. I have included the > Lispworks buffer first and then the SLIME buffer after. > The versions of the packages that I am using are as follows: > - asdf-system-connections 0.8.3 > - cl-containers 0.8.3 > - cl-fad 0.5.1 > - cl-markdown 0.8.6 > - cl-ppcre 1.2.19 > - cl-who 0.6.3 > - closer-mop (Feb 06 version) > - defsystem-compatibility (Fri Jun 23 version) > - html-encode 1.2 > - lw-compat 0.22 > - lw-doc 0.1.5 > - metabang-bind (Feb 5 version) > - metatiltiies 0.6.3 > - moptilities (0.3.4) > > - Luke >>>>> Start Lispworks buffer error > > ;;; Compiling file c:\home\bin\clisp\asdf\cl-markdown\dev > \package.lisp ... > ;;; Safety = 3, Speed = 1, Space = 1, Float = 1, Interruptible = 0 > ;;; Compilation speed = 1, Debug = 2, Fixnum safety = 3 > ;;; Source level debugging is on > ;;; Source file recording is on > ;;; Cross referencing is on > ; (TOP-LEVEL-FORM 1) > ; (TOP-LEVEL-FORM 2) > > **++++ Error in (PACKAGE "CL-MARKDOWN"): > No symbol named "SYSTEM-RELATIVE-PATHNAME" is accessible in > #:DEFSYSTEM-COMPATIBILITY. > > **++++ Error in (PACKAGE "CL-MARKDOWN-USER"): > Package CL-MARKDOWN not found. > ; (TOP-LEVEL-FORM 3) > ; *** 2 errors detected, no fasl file produced. > <<<<< End Lispworks buffer error > >>>>>> Start SLIME buffer error > > erred while invoking #<ASDF:COMPILE-OP NIL 21EB9EE4> on > #<ASDF:CL-SOURCE-FILE "package" 21EBFC7C> > [Condition of type ASDF:COMPILE-ERROR] > Restarts: > 0: [RETRY] Retry performing #<ASDF:COMPILE-OP NIL 21EB9EE4> on > #<ASDF:CL-SOURCE-FILE "package" 21EBFC7C>. > 1: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL 21EB9EE4> on > #<ASDF:CL-SOURCE-FILE "package" 21EBFC7C> as having been successful. > 2: [ABORT-REQUEST] Abort handling SLIME request. > 3: [ABORT] Quit process. > Backtrace: > 0: CONDITIONS::CONDITIONS-ERROR (:INVISIBLEP T ASDF:COMPILE-ERROR > (:COMPONENT #<ASDF:CL-SOURCE-FILE "package" 21EBFC7C> :OPERATION > #<ASDF:COMPILE-OP NIL 21EB9EE4>)) > 1: ("Anonymous compiled function ~s" #<function 203E5E4A>) NIL > 2: (SUBFUNCTION 1 ASDF:OPERATE) NIL > 3: COMPILER::DO-COMPILATION-UNIT (#<closure (SUBFUNCTION 1 > ASDF:OPERATE) 21EC17A2> T NIL) > 4: COMPILER::WITH-COMPILATION-UNIT-INTERNAL (#<closure > (SUBFUNCTION 1 ASDF:OPERATE) 21EC17A2> &KEY NIL NIL NIL) > 5: ASDF:OPERATE (ASDF:LOAD-OP :CL-MARKDOWN &REST NIL &KEY T NIL > "<&ALLOW-OTHER-KEYS>") > 6: SPECIAL::%EVAL-NOHOOK ((ASDF:OPERATE 'ASDF:LOAD-OP :CL-MARKDOWN)) > 7: IV:PROCESS-TOP-LEVEL (DSPEC:*CURRENT-FORM* #S > (LEXICAL::ENVIRONMENT :VARIABLES NIL :FUNCTIONS NIL :REMOTE- > ENVIRONMENT NIL) #<function LEXICAL:EVAL-WITH-ENV 20140F9A> > &OPTIONAL :EXECUTE) > 8: SWANK::EVAL-REGION ("(asdf:operate 'asdf:load-op :cl-markdown) > " > &OPTIONAL > T) > 9: (SUBFUNCTION 1 SWANK:LISTENER-EVAL) NIL > 10: SWANK::CALL-WITH-BUFFER-SYNTAX (#<closure (SUBFUNCTION 1 > SWANK:LISTENER-EVAL) 21E7524A>) > 11: SPECIAL::%EVAL-NOHOOK ((SWANK:LISTENER-EVAL "(asdf:operate > 'asdf:load-op :cl-markdown) > ")) > 12: IV:PROCESS-TOP-LEVEL (DSPEC:*CURRENT-FORM* #S > (LEXICAL::ENVIRONMENT :VARIABLES NIL :FUNCTIONS NIL :REMOTE- > ENVIRONMENT NIL) #<function LEXICAL:EVAL-WITH-ENV 20140F9A> > &OPTIONAL :EXECUTE) > 13: (SUBFUNCTION 1 SWANK::EVAL-FOR-EMACS) NIL > 14: (SUBFUNCTION 1 (TOP-LEVEL-FORM 52)) (#<function SWANK:SWANK- > DEBUGGER-HOOK 21FFD6E2> #<closure (SUBFUNCTION 1 SWANK::EVAL-FOR- > EMACS) 21E75312>) > 15: FUNCALL (SWANK::EVAL-FOR-EMACS &REST > ((SWANK:LISTENER-EVAL "(asdf:operate > 'asdf:load-op :cl-markdown) > ") > "COMMON-LISP-USER" > 7)) > <<<<< End SLIME buffer error -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[cl-markdown-devel] announce: CL-Markdown 0.8.5
by Gary King 06 Feb '07

06 Feb '07

Today's update to [CL-Markdown][] marks brings more fixes to paragraphs and entity encoding. It also finds CL-Markdown saying goodbye to [HTML-Encode][] (because I decided that because I only used a tiny bit of it and because "less dependencies" is a good thing, it was better just to pull the bit out and make it my own...). Oh, there's one more thing: if you're generating HTML (and, frankly, who isn't nowadays), then CL-Markdown looks for the following properties: * author * description * copyright * keywords * date * refresh * expires If it finds one, it adds the appropriate META tag to the HTML header (i.e., either `name` or `http-equiv`). There is no sanity checking but it should handle the basics. If it doesn't, let me know. [HTML-Encode]: http://www.cliki.net/html-encode [CL-Markdown]: http://common-lisp.net/project/cl-markdown/ [Trivial-shell]: http://common-lisp.net/project/trivial-shell/ [comparison]: http://common-lisp.net/project/cl-markdown/comparison- tests/ -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[cl-markdown-devel] author property broken?
by Hans Halvorson 06 Feb '07

06 Feb '07

I am running tests with 0.8.4, and the {set-property Author ...} seems to be malfunctioning. For example: (let ((*parse-active-functions* '(table-of-contents set-property)) (*render-active-functions* '(table-of-contents property))) (markdown "{set-property html t} {set-property title My best summer vacation ever} {set-property style-sheet my-style.css} {set-property Author Gary W. King} Some text." :stream nil :format :html)) => #<DOCUMENT {A7D72B9}> "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\"> <html> <head> <title>My best summer vacation ever</title> <link type='text/css' href='my-style.css' rel='stylesheet' /> </head> <body><p> Some text. </p> </body> </html>" Cheers, Hans

1 1

[cl-markdown-devel] announcing cl-markdown 0.8.4
by Gary King 05 Feb '07

05 Feb '07

Thanks to some more bug finding by Hans Halvorson, [CL-Markdown][] now correctly lower-cases paragraph markers and handles hard returns more correctly. I've also extended the test-suite (using the new features of [Trivial-shell][]) so that it's easier to test compatibility between markdown and CL-Markdown. To the end, I've also re-generated the [comparison][] page; There are a few new problems (cf. auto links and the syntax-compare!) so I'll hope to get to 0.8.5 very soon. [CL-Markdown]: http://common-lisp.net/project/cl-markdown/ [Trivial-shell]: http://common-lisp.net/project/trivial-shell/ [comparison]: http://common-lisp.net/project/cl-markdown/comparison- tests/ -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[cl-markdown-devel] list items with newlines
by Hans Halvorson 03 Feb '07

03 Feb '07

(Perl)-markdown and cl-markdown give different outputs for the following input: * A first list item with a hard return * A second list item The perl-markdown output: <ul> <li>A first list item with a hard return</li> <li>A second list item</li> </ul> The cl-markdown output: <ul> <li>A first list item</li> </ul>with a hard return <ul> <li>A second list item</li> </ul> So, cl-markdown reads the newline followed by a line not beginning with "*" as indicating that the list item and list are ending. For further diagnosis, I did: (cl-containers:contents (chunks (chunk-source "* A first list item with a hard return * A second list item"))) => #(#<CHUNK NIL/1 1 lines LINE-STARTS-WITH-BULLET-P LINE-IS-NOT-EMPTY-P> #<CHUNK NIL/0 1 lines LINE-IS-NOT-EMPTY-P LINE-STARTS-WITH-BULLET-P> #<CHUNK NIL/1 1 lines LINE-STARTS-WITH-BULLET-P END-OF-DOCUMENT>) But at this point, I can't tell what is happening: is the second chunk (line) being misread? Or is this OK, and the problem occurs later, e.g. when the first and second chunks should be merged? Thanks, Hans

2 1

[cl-markdown-devel] links, lists, headings
by Hans Halvorson 02 Feb '07

02 Feb '07

I have come across some weird behavior in the interaction between links, lists, and headings (cl-markdown v 0.8.2). The following two forms act as they should: (markdown "## Common Lisp * An item with a link [link](link.html) and some following text." :format :html :stream nil) => "<H2>Common Lisp </H2> <UL><LI>An item with a link <a href=\"link.html\">link</a> and some following text. </LI> </UL>" (markdown "## Common Lisp * An item with a link [link](link.html) and some following text. * Another item" :format :html :stream nil) => "<H2>Common Lisp </H2> <UL><LI>An item with a link <a href=\"link.html\">link</a> and some following text. </LI> <LI>Another item </LI> </UL>" But the following form wraps the first list item in paragraph tags: (markdown "## Common Lisp * An item with a link [link](link.html) and some following text. ## A second level heading * Another item" :format :html :stream nil) => "<H2>Common Lisp </H2> <UL><LI><P>An item with a link <a href=\"link.html\">link</a> and some following text. </P></LI> </UL><H2>A second level heading </H2> <UL><LI>Another item </LI> </UL>" I also compared the output for this last string with the output from Perl-markdown, and it does *not* add the paragraph tags. By the way, shouldn't the xhtml tags be lower case by default? Thanks, Hans

2 3

[cl-markdown-devel] Announce 0.8.3
by Gary King 02 Feb '07

02 Feb '07

Thanks to Hans Halvorson for noticing both that [CL-Markdown][] wasn't handling list item paragraph tags properly *and* that it was generating HTML tag in ALL UPPERCASE. Both of these items are fixed in version 0.8.3 ([changelog][]). [CL-Markdown]: http://common-lisp.net/project/cl-markdown/ [changelog]: http://common-lisp.net/project/cl-markdown/changelog.html -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[cl-markdown-devel] Re: ASDF-METATILITIES::DEFSYSTEM-COMPATIBILITY not found
by Gary King 18 Jan '07

18 Jan '07

Hi Luke, I think I'm getting a handle as to what is going wrong here but I'm not quite sure whether it's ASDF's "fault", ASDF-System-Connections "fault" or just a misunderstanding between the two. One thing I noticed that may be contributing to the problem is that there are two defsystem-connections for bind-and-metatilities. What happens if you rename the second one to bind-and-defclass* (which is what it should be called in any case)? I'll follow up with you later today with what I hope will be a better understanding of what is going wrong. regards, On Jan 17, 2007, at 8:48 PM, Luke J Crook wrote: > Thanks Gary. Things are progressing but now it throws the error > below. Is this somehow related to building on Windows instead of > Linux? > Thanks, > - Luke > > No applicable methods for #<STANDARD-GENERIC-FUNCTION GENERIC- > FUNCTION-NAME 203A605A> with args (NIL) > [Condition of type SIMPLE-ERROR] > Restarts: > 0: [CONTINUE] Call #<STANDARD-GENERIC-FUNCTION GENERIC-FUNCTION- > NAME 203A605A> again > 1: [NIL] Try loading c:\home\bin\clisp\asdf\metabang-bind\metabang- > bind.asd again. > 2: [NIL] Give up loading c:\home\bin\clisp\asdf\metabang-bind > \metabang-bind.asd. > 3: [NIL] Try loading another file instead of c:\home\bin\clisp\asdf > \metabang-bind\metabang-bind.asd. > 4: [ABORT-REQUEST] Abort handling SLIME request. > 5: [ABORT] Quit process. > Backtrace: > 0: CONDITIONS::CONDITIONS-ERROR (:INVISIBLEP T "No applicable > methods for ~S with args ~S" (#<STANDARD-GENERIC-FUNCTION GENERIC- > FUNCTION-NAME 203A605A> (NIL))) > 1: CERROR ("Call ~S again" "No applicable methods for ~S with args > ~S" &REST (#<STANDARD-GENERIC-FUNCTION GENERIC-FUNCTION-NAME > 203A605A> (NIL))) > 2: (METHOD NO-APPLICABLE-METHOD (T)) (#<STANDARD-GENERIC-FUNCTION > GENERIC-FUNCTION-NAME 203A605A> &REST (NIL)) > 3: CLOS::MAYBE-FLUSH-MAKE-INSTANCE-KEYWORD-CACHE (#<STANDARD- > METHOD NIL (:AFTER) (#<STANDARD-CLASS ASDF:LOAD-OP 21778B0C> (EQL > #<ASDF::SYSTEM-CONNECTION "bind-and-metatilities" 214F08F4>)) > 214FB24C>) > 4: (METHOD REMOVE-METHOD (STANDARD-GENERIC-FUNCTION METHOD)) > (#<STANDARD-GENERIC-FUNCTION ASDF:EXPLAIN 21748262> #<STANDARD- > METHOD NIL (:AFTER) (#<STANDARD-CLASS ASDF:LOAD-OP 21778B0C> (EQL > #<ASDF::SYSTEM-CONNECTION "bind-and-metatilities" 214F08F4>)) > 214FB24C>) -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 1

[cl-markdown-devel] Re: ASDF-METATILITIES::DEFSYSTEM-COMPATIBILITY not found
by Gary King 18 Jan '07

18 Jan '07

Hi Luke, The asdf-metatilities package is defined in the metatilities.asd file. Metatilities depends on all of (metatilities-base moptilities cl-containers metabang-bind defsystem-compatibility cl-fad asdf-system-connections) (Which is either gross of good, I suppose, depending on your point of view vis-a-vis software sharing, forking, etc... <smile>). It sounds as if you don't have defsystem-compatibility yet. Check http://www.cliki.net/defsystem-compatibility or http://common-lisp.net/project/cl-containers/defsystem-compatibility/ Please let me know if this do the trick for you and how the rest of your work with cl-markdown goes. thanks, On Jan 17, 2007, at 7:12 PM, Luke J Crook wrote: > ASDF-METATILITIES::DEFSYSTEM-COMPATIBILITY -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[cl-markdown-devel] new version 0.8.1
by Gary King 09 Oct '06

09 Oct '06

* Fixed bug where bullet marker was not being stripped from bullet lines (e.g., leaving extra *'s). * Fixed load-order bug where *render-active-functions* and *parse- active-functions* were not being treated as specials. -- Gary Warren King, metabang.com Cell: (413) 885 9127 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

1 0

[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 23 May '06

23 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

cl-markdown-devel