browsing on github

[Jason Dagit]

On Thu, Apr 25, 2013 at 12:21 AM, Jan Stolarek <jan.stolarek at p.lodz.pl> wrote:
> Opening a ticket is a good idea - this problem has been iritating me as well and in fact I almost
> gave up on browsing GHC code on github.

+1

I use "raw" view for .lhs files as a workaround.

>
> As a side note it seems to me that writing literate Haskell is not really popular and I would be
> happy to see the source code of GHC converted to .hs one day (I wouldn't mind converting some of
> it myself).

My experience has been that outside of papers, tutorials, and blog
posts that lhs is more trouble than it's worth. The downside is that
haddock is not a very good markup language. It's just fine for plain
text comments, but if you want to say something mathematical in a
haddock comment it may get the wrong idea (x /y + a/b, would render y
+ a in italics and not show the divisions). So I don't think we should
convert them unless there is a stronger reason than github rendering.

I think the right thing is to leave the .lhs files how they are for
now and try to convince github to stop treating .lhs as markdown.

Jason