Changes between Version 1 and Version 2 of LiterateMarkdown


Ignore:
Timestamp:
Jun 19, 2013 11:59:54 PM (10 months ago)
Author:
elliottt
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LiterateMarkdown

    v1 v2  
    11= Literate Markdown = 
    22 
    3 The purpose of this addition is to allow GHC to accept markdown files as input, keeping unlabeled code blocks, and haskell marked code blocks in the output of unlit. 
     3Markdown has grown in popularity since github started encouraging people to write their documentation with it. 
     4Github highlights the source according to how it's labeled, so the haskell code blocks look nice, as do the HTML blocks. 
     5As an example, here is a blog post written in markdown and rendered by github's source view (please ignore the metadata at the top of the rendered output, as it's only relevant to octopress): 
     6 
     7https://github.com/elliottt/elliottt.github.com/blob/source/source/_posts/2013-02-19-serenade-in-haskell.markdown 
     8 
     9And here is the source: 
     10 
     11https://raw.github.com/elliottt/elliottt.github.com/source/source/_posts/2013-02-19-serenade-in-haskell.markdown 
     12 
     13As you can see, the source is a haskell module, and if GHC accepted .md or .markdown as input, this blog post would be executable. 
    414 
    515== Current Literate Processing ==