From hhalvors at Princeton.EDU  Fri Feb  2 16:21:58 2007
From: hhalvors at Princeton.EDU (Hans Halvorson)
Date: Fri, 02 Feb 2007 11:21:58 -0500
Subject: [cl-markdown-devel] links, lists, headings
Message-ID: <87fy9oedi1.wl%hhalvors@Princeton.EDU>

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



From gwking at metabang.com  Fri Feb  2 18:21:43 2007
From: gwking at metabang.com (Gary King)
Date: Fri, 2 Feb 2007 13:21:43 -0500
Subject: [cl-markdown-devel] links, lists, headings
In-Reply-To: <87fy9oedi1.wl%hhalvors@Princeton.EDU>
References: <87fy9oedi1.wl%hhalvors@Princeton.EDU>
Message-ID: <B7795A6D-B930-4F3C-91A9-1D89117F504C@metabang.com>

Hi Hans,

Thanks for your bug report. I agree that the first list item in the  
last example should not have paragraph tags around it.

> By the way, shouldn't the xhtml tags be lower case by default?

Whoopts, yes. I've been using Allegro Common Lisp in "modern" mode  
lately and it translates my keywords like :h1 into :h1 which outputs  
as "h1". ANSI Common Lisp, of course, reads :h1 as :H1 and produces  
"H1".

This will be corrected in the next release (which will happen as soon  
as I figure out how to fix the first bug you found!

thanks again,
--
Gary Warren King, metabang.com
Cell: (413) 885 9127
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM






From gwking at metabang.com  Fri Feb  2 19:10:01 2007
From: gwking at metabang.com (Gary King)
Date: Fri, 2 Feb 2007 14:10:01 -0500
Subject: [cl-markdown-devel] Announce 0.8.3
Message-ID: <3331585D-304F-48F6-81F0-747246629961@metabang.com>

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






From hhalvors at Princeton.EDU  Fri Feb  2 20:19:31 2007
From: hhalvors at Princeton.EDU (Hans Halvorson)
Date: Fri, 02 Feb 2007 15:19:31 -0500
Subject: [cl-markdown-devel] links, lists, headings
In-Reply-To: <B7795A6D-B930-4F3C-91A9-1D89117F504C@metabang.com>
References: <87fy9oedi1.wl%hhalvors@Princeton.EDU>
	<B7795A6D-B930-4F3C-91A9-1D89117F504C@metabang.com>
Message-ID: <87d54suxbg.wl%hhalvors@Princeton.EDU>

Gary,

Thank you for your very quick attention to these issues.  I just
grabbed version 0.8.3, and can confirm that it fixes the list issue,
as well as the uppercase <H#> tags issue.  But the tag fix does not
seem to have been propagated to all html tags, e.g. paragraph tags are
still coming out as <P>.  For example,

(markdown "

New paragraph
                        " :format :html :stream nil)


=> "<P>New paragraph </P>"


Best wishes,
Hans

At Fri, 02 Feb 2007 13:21:43 -0500,
Gary King wrote:
> 
> Hi Hans,
> 
> Thanks for your bug report. I agree that the first list item in the  
> last example should not have paragraph tags around it.
> 
> > By the way, shouldn't the xhtml tags be lower case by default?
> 
> Whoopts, yes. I've been using Allegro Common Lisp in "modern" mode  
> lately and it translates my keywords like :h1 into :h1 which outputs  
> as "h1". ANSI Common Lisp, of course, reads :h1 as :H1 and produces  
> "H1".
> 
> This will be corrected in the next release (which will happen as soon  
> as I figure out how to fix the first bug you found!
> 
> thanks again,
> --
> Gary Warren King, metabang.com
> Cell: (413) 885 9127
> Fax: (206) 338-4052
> gwkkwg on Skype * garethsan on AIM
> 
> 
> 
> 


From gwking at metabang.com  Fri Feb  2 22:30:57 2007
From: gwking at metabang.com (Gary King)
Date: Fri, 2 Feb 2007 17:30:57 -0500
Subject: [cl-markdown-devel] links, lists, headings
In-Reply-To: <87d54suxbg.wl%hhalvors@Princeton.EDU>
References: <87fy9oedi1.wl%hhalvors@Princeton.EDU>
	<B7795A6D-B930-4F3C-91A9-1D89117F504C@metabang.com>
	<87d54suxbg.wl%hhalvors@Princeton.EDU>
Message-ID: <80D2A642-EEBD-443F-B3B9-36B1296F99BB@metabang.com>

Ack! My bad. I forgot to test on a lisp other than Allegro modern  
mode -- head slap.

I fix this later tonight (or over the weekend).


On Feb 2, 2007, at 3:19 PM, Hans Halvorson wrote:

> Gary,
>
> Thank you for your very quick attention to these issues.  I just
> grabbed version 0.8.3, and can confirm that it fixes the list issue,
> as well as the uppercase <H#> tags issue.  But the tag fix does not
> seem to have been propagated to all html tags, e.g. paragraph tags are
> still coming out as <P>.  For example,
>
> (markdown "
>
> New paragraph
>                         " :format :html :stream nil)
>
>
> => "<P>New paragraph </P>"
>
>
> Best wishes,
> Hans
>
> At Fri, 02 Feb 2007 13:21:43 -0500,
> Gary King wrote:
>>
>> Hi Hans,
>>
>> Thanks for your bug report. I agree that the first list item in the
>> last example should not have paragraph tags around it.
>>
>>> By the way, shouldn't the xhtml tags be lower case by default?
>>
>> Whoopts, yes. I've been using Allegro Common Lisp in "modern" mode
>> lately and it translates my keywords like :h1 into :h1 which outputs
>> as "h1". ANSI Common Lisp, of course, reads :h1 as :H1 and produces
>> "H1".
>>
>> This will be corrected in the next release (which will happen as soon
>> as I figure out how to fix the first bug you found!
>>
>> thanks again,
>> --
>> Gary Warren King, metabang.com
>> Cell: (413) 885 9127
>> Fax: (206) 338-4052
>> gwkkwg on Skype * garethsan on AIM
>>
>>
>>
>>

--
Gary Warren King, metabang.com
Cell: (413) 885 9127
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM






From hhalvors at Princeton.EDU  Sat Feb  3 10:59:44 2007
From: hhalvors at Princeton.EDU (Hans Halvorson)
Date: Sat, 03 Feb 2007 05:59:44 -0500
Subject: [cl-markdown-devel] list items with newlines
Message-ID: <87zm7vjylb.wl%hhalvors@Princeton.EDU>

(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


From gwking at metabang.com  Sat Feb  3 21:48:08 2007
From: gwking at metabang.com (Gary King)
Date: Sat, 3 Feb 2007 16:48:08 -0500
Subject: [cl-markdown-devel] list items with newlines
In-Reply-To: <87zm7vjylb.wl%hhalvors@Princeton.EDU>
References: <87zm7vjylb.wl%hhalvors@Princeton.EDU>
Message-ID: <0FB70F33-C158-46DA-A561-2A2211B7D77C@metabang.com>

Hans,

Thank you so much for these little test cases; I've been hoping to  
slowly clean things up and get the corner cases correct. These will  
help me do so so please keep sending them if it's not too much a  
bother. I will be adding them to a LIFT regression suite to make sure  
that things keep working.

regards,

On Feb 3, 2007, at 5:59 AM, Hans Halvorson wrote:

> (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
> _______________________________________________
> cl-markdown-devel mailing list
> cl-markdown-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-markdown-devel

--
Gary Warren King, metabang.com
Cell: (413) 885 9127
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM






From gwking at metabang.com  Mon Feb  5 15:26:40 2007
From: gwking at metabang.com (Gary King)
Date: Mon, 5 Feb 2007 10:26:40 -0500
Subject: [cl-markdown-devel] announcing cl-markdown 0.8.4
Message-ID: <29F4C908-345B-4CD8-A26D-FEB57E0556EE@metabang.com>

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






From hhalvors at Princeton.EDU  Mon Feb  5 23:14:08 2007
From: hhalvors at Princeton.EDU (Hans Halvorson)
Date: Mon, 05 Feb 2007 18:14:08 -0500
Subject: [cl-markdown-devel] author property broken?
Message-ID: <878xfckxj3.wl%hhalvors@Princeton.EDU>

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


From hhalvors at Princeton.EDU  Mon Feb  5 23:29:44 2007
From: hhalvors at Princeton.EDU (Hans Halvorson)
Date: Mon, 05 Feb 2007 18:29:44 -0500
Subject: [cl-markdown-devel] author property broken?
In-Reply-To: <878xfckxj3.wl%hhalvors@Princeton.EDU>
References: <878xfckxj3.wl%hhalvors@Princeton.EDU>
Message-ID: <877iuwkwt3.wl%hhalvors@Princeton.EDU>

Oops; I see now that 'generate-html-header' (in /dev/html.lisp)
doesn't try to put in an author field.

(defun generate-html-header ()
  (generate-doctype)
  (format *output-stream* "~&<html>~&<head>")
  (awhen (document-property "title")
    (format *output-stream* "~&<title>~a</title>" it))
  (awhen (document-property "style-sheet")
    (unless (search ".css" it)
      (setf it (concatenate 'string it ".css")))
    (format *output-stream* "~&<link type='text/css' href='~a' rel='stylesheet' />" it))
  (format *output-stream* "~&</head>~&<body>"))

So, I should instead say: "Feature request: add author field to the
html-header?"

Best wishes,
Hans

At Mon, 05 Feb 2007 18:14:08 -0500,
Hans Halvorson wrote:
> 
> 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
> _______________________________________________
> cl-markdown-devel mailing list
> cl-markdown-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-markdown-devel


From gwking at metabang.com  Tue Feb  6 22:34:26 2007
From: gwking at metabang.com (Gary King)
Date: Tue, 6 Feb 2007 17:34:26 -0500
Subject: [cl-markdown-devel] announce: CL-Markdown 0.8.5
Message-ID: <11AB20F8-08B8-4F9C-8949-C44F440566E9@metabang.com>

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






From gwking at metabang.com  Wed Feb 21 17:38:03 2007
From: gwking at metabang.com (Gary King)
Date: Wed, 21 Feb 2007 12:38:03 -0500
Subject: [cl-markdown-devel] Re: cl-markdown (hangs head in shame)
In-Reply-To: <20070221043444.70381.qmail@mail.superb.net>
References: <20070221043444.70381.qmail@mail.superb.net>
Message-ID: <56302DBF-E169-403E-AB9D-B8EB2ED910D7@metabang.com>

(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






From hhalvors at Princeton.EDU  Mon Feb 26 14:50:55 2007
From: hhalvors at Princeton.EDU (Hans Halvorson)
Date: Mon, 26 Feb 2007 09:50:55 -0500
Subject: [cl-markdown-devel] div tags
Message-ID: <87odnhrn00.wl%hhalvors@Princeton.EDU>

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


From gwking at metabang.com  Tue Feb 27 01:42:55 2007
From: gwking at metabang.com (Gary King)
Date: Mon, 26 Feb 2007 20:42:55 -0500
Subject: [cl-markdown-devel] div tags
In-Reply-To: <87odnhrn00.wl%hhalvors@Princeton.EDU>
References: <87odnhrn00.wl%hhalvors@Princeton.EDU>
Message-ID: <6C685313-27CE-46BE-903C-DAB0EEB0CCC0@metabang.com>

Hi Hans,

Thanks for this bug report. I'll look soon.


On Feb 26, 2007, at 9:50 AM, Hans Halvorson wrote:

> 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
> _______________________________________________
> cl-markdown-devel mailing list
> cl-markdown-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-markdown-devel

--
Gary Warren King, metabang.com
Cell: (413) 885 9127
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM






From gwking at metabang.com  Tue Feb 27 01:44:27 2007
From: gwking at metabang.com (Gary King)
Date: Mon, 26 Feb 2007 20:44:27 -0500
Subject: [cl-markdown-devel] Re: feature request (user guide)
In-Reply-To: <877iu5b7et.wl%hhalvors@Princeton.EDU>
References: <877iu5b7et.wl%hhalvors@Princeton.EDU>
Message-ID: <D2C8F1CF-5857-47C8-A721-92FB15CFF64E@metabang.com>

(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






From hhalvors at Princeton.EDU  Tue Feb 27 08:39:30 2007
From: hhalvors at Princeton.EDU (Hans Halvorson)
Date: Tue, 27 Feb 2007 03:39:30 -0500
Subject: [cl-markdown-devel] manual line breaking
Message-ID: <87ejocata5.wl%hhalvors@Princeton.EDU>

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


From gwking at metabang.com  Tue Feb 27 15:15:05 2007
From: gwking at metabang.com (Gary King)
Date: Tue, 27 Feb 2007 10:15:05 -0500
Subject: [cl-markdown-devel] div tags
In-Reply-To: <87odnhrn00.wl%hhalvors@Princeton.EDU>
References: <87odnhrn00.wl%hhalvors@Princeton.EDU>
Message-ID: <2CD82F9F-F381-4E46-9F9A-70C9C02762DE@metabang.com>

Hi Hans,

I have a fix for the errant paragraph tags but I'm not sure I like  
that Markdown doesn't apply markdown inside the blocks. I.e., I'd  
rather that

<div>

## Header

</div

become

<div>
<h2>Header</h2>
</div>

What's your opinion? Is there a justification for one behavior over  
the other.

thanks,

On Feb 26, 2007, at 9:50 AM, Hans Halvorson wrote:

> 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
> _______________________________________________
> cl-markdown-devel mailing list
> cl-markdown-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-markdown-devel

--
Gary Warren King, metabang.com
Cell: (413) 885 9127
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM






From hhalvors at Princeton.EDU  Tue Feb 27 16:15:00 2007
From: hhalvors at Princeton.EDU (Hans Halvorson)
Date: Tue, 27 Feb 2007 11:15:00 -0500
Subject: [cl-markdown-devel] div tags
In-Reply-To: <2CD82F9F-F381-4E46-9F9A-70C9C02762DE@metabang.com>
References: <87odnhrn00.wl%hhalvors@Princeton.EDU>
	<2CD82F9F-F381-4E46-9F9A-70C9C02762DE@metabang.com>
Message-ID: <87hct737cr.wl%hhalvors@Princeton.EDU>

Gary,

I agree with your first impulse.  It would be very natural to use
<div> tags to split a document up into chunks, but then to use
markdown syntax within the individual chunks.

For a precedent at deviating from the original markdown syntax, you
might look at:
http://sophos.berkeley.edu/macfarlane/pandoc/README.html (see the
section on "Embedded html").

Thanks for your attention to these issues.

Best,
Hans

At Tue, 27 Feb 2007 10:15:05 -0500,
Gary King wrote:
> 
> Hi Hans,
> 
> I have a fix for the errant paragraph tags but I'm not sure I like  
> that Markdown doesn't apply markdown inside the blocks. I.e., I'd  
> rather that
> 
> <div>
> 
> ## Header
> 
> </div
> 
> become
> 
> <div>
> <h2>Header</h2>
> </div>
> 
> What's your opinion? Is there a justification for one behavior over  
> the other.
> 
> thanks,
> 
> On Feb 26, 2007, at 9:50 AM, Hans Halvorson wrote:
> 
> > 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
> > _______________________________________________
> > cl-markdown-devel mailing list
> > cl-markdown-devel at common-lisp.net
> > http://common-lisp.net/cgi-bin/mailman/listinfo/cl-markdown-devel
> 
> --
> Gary Warren King, metabang.com
> Cell: (413) 885 9127
> Fax: (206) 338-4052
> gwkkwg on Skype * garethsan on AIM
> 
> 
> 
> 


From hutch at recursive.ca  Wed Feb 28 14:24:41 2007
From: hutch at recursive.ca (Bob Hutchison)
Date: Wed, 28 Feb 2007 09:24:41 -0500
Subject: [cl-markdown-devel] div tags
In-Reply-To: <2CD82F9F-F381-4E46-9F9A-70C9C02762DE@metabang.com>
References: <87odnhrn00.wl%hhalvors@Princeton.EDU>
	<2CD82F9F-F381-4E46-9F9A-70C9C02762DE@metabang.com>
Message-ID: <2570D0A6-E3E6-4637-9CAA-AFFBBA2E8638@recursive.ca>

Hi Gary,

On 27-Feb-07, at 10:15 AM, Gary King wrote:

> Hi Hans,
>
> I have a fix for the errant paragraph tags but I'm not sure I like  
> that Markdown doesn't apply markdown inside the blocks. I.e., I'd  
> rather that
>
> <div>
>
> ## Header
>
> </div
>
> become
>
> <div>
> <h2>Header</h2>
> </div>
>
> What's your opinion? Is there a justification for one behavior over  
> the other.

I've seen arguments about this, but they tend to go on forever and so  
I tend to tune out.

You might consider what happens if you do:

<p>
## Header
</p>

For an alternative approach, you can look at maruku <http:// 
rubyforge.org/projects/maruku/> which is another Ruby implementation  
of markdown. Maruku adds an attribute it recognises to the html, so...

<div markdown="1">
## Header
</div>

will do as you want. Maruku will attempt to avoid doing something  
obviously wrong, e.g. it will not convert the heading inside a  
paragraph example from above since a heading is not allowed in a  
paragraph. Maruku will also strip the markdown attribute from the  
output. Unfortunately, using this input with the real markdown  
processor will not strip the attribute.

Textile will process the content inside html tags, and it will put  
headers inside paragraphs. That isn't so good.

You might want to worry about this when you have lots of time, it  
sounds like a bit of a can of worms to me.

Cheers,
Bob

>
> thanks,
>
> On Feb 26, 2007, at 9:50 AM, Hans Halvorson wrote:
>
>> 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
>> _______________________________________________
>> cl-markdown-devel mailing list
>> cl-markdown-devel at common-lisp.net
>> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-markdown-devel
>
> --
> Gary Warren King, metabang.com
> Cell: (413) 885 9127
> Fax: (206) 338-4052
> gwkkwg on Skype * garethsan on AIM
>
>
>
>
> _______________________________________________
> cl-markdown-devel mailing list
> cl-markdown-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-markdown-devel

----
Bob Hutchison                  -- blogs at <http://www.recursive.ca/ 
hutch/>
Recursive Design Inc.          -- <http://www.recursive.ca/>
Raconteur                      -- <http://www.raconteur.info/>
xampl for Ruby                 -- <http://rubyforge.org/projects/xampl/>