On 24.07.2011 13:11, Joris Putcuyps wrote:
On Sat, 23 Jul 2011 19:25:53 -0700
Greg Weber wrote:
[1] http://hackage.haskell.org/package/hamlet
The cabal file should be compact, and quite often the
description field is very lengthy.
I would like it alot if I could reference a README.??? (pand
On 24 July 2011 21:11, Joris Putcuyps wrote:
> On Sat, 23 Jul 2011 19:25:53 -0700
> Greg Weber wrote:
>
>> I think the haddock description field is a great barrior to
>> documentation. I don't want to clutter my cabal file with lengthy
>> documentation. Michael Snoyberg and I could not figure out
On Sat, 23 Jul 2011 19:25:53 -0700
Greg Weber wrote:
> I think the haddock description field is a great barrior to
> documentation. I don't want to clutter my cabal file with lengthy
> documentation. Michael Snoyberg and I could not figure out how to
> document the Hamlet syntax because there is
I think the haddock description field is a great barrior to documentation. I
don't want to clutter my cabal file with lengthy documentation.
Michael Snoyberg and I could not figure out how to document the Hamlet
syntax because there is no way (as far as I know) to have literal
unescaped, uninterpre
On 23 July 2011 21:33, Joris Putcuyps wrote:
> About your first point, I'm aware of that. It would have been
> nice if .cabal and haddock used markdown, this is very popular, thanks
> to pandoc. Then generating html, pdf, texinfo, ... would be very easy.
This has been suggested before, e.g.
http:
On Sat, 23 Jul 2011 10:47:18 +
Ivan Lazar Miljenovic wrote:
> On 23 July 2011 10:35, Joris Putcuyps
> wrote:
> > Hello everybody
> >
> > I'm looking for a way to avoid having two files with almost the same
> > information on github: README.markdown and package.cabal.
> >
> > As far as I can
Hi Joris,
not exactly what you are think about, but still maybe somewhat related.
I thought it would be nice to have support for literate Haskell in
README files (say README.lhs) on GitHub. I've done something similar
for WAI[1], using sed to transform it to markdown, native support
support for RE
On 23 July 2011 10:35, Joris Putcuyps wrote:
> Hello everybody
>
> I'm looking for a way to avoid having two files with almost the same
> information on github: README.markdown and package.cabal.
>
> As far as I can tell, a new github README parser[1] can be written,
> but it only supports README
Hello everybody
I'm looking for a way to avoid having two files with almost the same
information on github: README.markdown and package.cabal.
As far as I can tell, a new github README parser[1] can be written,
but it only supports README files with different extensions and requires
either ruby o
