[GHC] #4836: literate markdown not handled correctly by unlit
GHC
ghc-devs at haskell.org
Sat Jun 7 16:03:56 UTC 2014
#4836: literate markdown not handled correctly by unlit
----------------------------------------------+----------------------------
Reporter: guest | Owner:
Type: bug | Status: new
Priority: low | Milestone: 7.6.2
Component: Compiler | Version: 7.0.1
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
Type of failure: GHC rejects valid program | Unknown/Multiple
Test Case: | Difficulty: Unknown
Blocking: | Blocked By:
| Related Tickets: #7120
----------------------------------------------+----------------------------
Comment (by elliottt):
I've had success using this with octopress, with this page as an example:
https://github.com/elliottt/elliottt.github.com/blob/source/source/_posts/2013-02-19
-serenade-in-haskell.markdown
I used ```haskell as the starting block, so that github would highlight
the haskell blocks, though ``` also works.
Do you know if BlogLiterally will process the fenced code blocks? I know
that pandoc is happy to process them, so I figured that it should just
work with anything that depends on that. Additionally, bird tracks in
markdown are for quoted blocks, not code, so if that's how BlogLiterally
is expecting to find the code, that could be a problem.
Does BlogLiterally process .lhs files? If so, that could also be a
problem, as markdown processing requires the .md extension, instead of
.lhs. The reason for this is that .lhs processing allows CPP macros, but
in markdown the # means a section header. The different extension signals
different flags to unlit.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/4836#comment:15>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list