-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/13 20:52, Carter Schonwald wrote:
> indeed. That approach seems like the most likely to be successful
> within the scope of a single summer.
>
> That said, this does raise the question of what needs to be fixed
> up / added to the haddock gr
indeed. That approach seems like the most likely to be successful within
the scope of a single summer.
That said, this does raise the question of what needs to be fixed up /
added to the haddock grammar to
a) make it a rich target for pandoc
b) make sure the augmented haddock grammar is human fri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/13 09:26, Andrew Butterfield wrote:
> My 2c (before such coins disappear...)
>
> On 2 May 2013, at 09:14, Petr Pudlák wrote:
>
>> Hi,
>>
>>
>> Personally I'd incline to choose some existing, well-established
>> markup language with formal
My 2c (before such coins disappear...)
On 2 May 2013, at 09:14, Petr Pudlák wrote:
> Hi,
>
>
> Personally I'd incline to choose some existing, well-established markup
> language with formal specification that supports math (hopefully there is
> one).
So TeX/LaTeX is out then :-(
---
Hi,
It seems that during the recent suggestions about what markup to choose
(Markdown, Creole, Asciidoc, etc.), we've forgotten about one of the goals
that seem very important to me for Haskell: the ability to write *math
formulas*. I have experienced on StackExchange that just adding MathJAX to
M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/13 06:57, Ben wrote:
> sorry, i was only trying to make a helpful suggestion!
>
> just to clarify: i'm not championing asciitext (or any other
> format) -- i only heard about it recently in a comment on
>
> http://www.codinghorror.com/blog/2
sorry, i was only trying to make a helpful suggestion!
just to clarify: i'm not championing asciitext (or any other format) -- i only
heard about it recently in a comment on
http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html
i checked it out and it sounded cool, so i thought i
On 30 April 2013 09:28, Richard A. O'Keefe wrote:
>
> On 29/04/2013, at 10:04 PM, kudah wrote:
>
>> On Mon, 29 Apr 2013 18:04:47 +1200 "Richard A. O'Keefe"
>> wrote:
>>
>>> so that there is no possibility of catching errors early;
>>> by definition in that processor there are no errors.
>>
>> Had
On 29/04/2013, at 10:04 PM, kudah wrote:
> On Mon, 29 Apr 2013 18:04:47 +1200 "Richard A. O'Keefe"
> wrote:
>
>> so that there is no possibility of catching errors early;
>> by definition in that processor there are no errors.
>
> Haddock's markup isn't any better in that regard.
Did I praise
On Mon, 29 Apr 2013 18:04:47 +1200 "Richard A. O'Keefe"
wrote:
> so that there is no possibility of catching errors early;
> by definition in that processor there are no errors.
Haddock's markup isn't any better in that regard. I spent two hours on
my first day with haddock figuring out that I n
On 29 April 2013 18:16, Alexander Kjeldaas wrote:
> I see the pluggable markup being pushed in this thread again.
>
> I just want to remind everybody that we currently have a flavor of a markup
> issue on github.
>
> The ghc source code uses literal haskell, and it does not work well on
> github.
I see the pluggable markup being pushed in this thread again.
I just want to remind everybody that we currently have a flavor of a markup
issue on github.
The ghc source code uses literal haskell, and it does not work well on
github.
http://www.haskell.org/pipermail/ghc-devs/2013-April/001099.ht
I should add that as a consumer of Haddock documentation
I can testify that fancier styling (in whatever format)
would be of little benefit to _me_. What I need is more
plain text and more examples.
To be perfectly honest, most of the time when looking at
a Haddock page, I end up clicking on the
On 29/04/2013, at 4:18 PM, Chris Smith wrote:
>
> My point was not anything at all to do with programming. It was about
> writing comments, which is fundamentally a communication activity. That
> makes a difference. It's important to keep in mind that the worst possible
> consequence of get
On Apr 28, 2013 6:42 PM, "Alexander Solla" wrote:
> I think that much has to do with the historical division in computer
science. We have mathematics on the right hand, and electrical engineering
on the wrong one.
I've been called many things, but electrical engineer is a new one!
My point was
On Mon, Apr 29, 2013 at 8:42 AM, Alexander Solla wrote:
> I've been scoffed at during interviews for saying I solve problems on
> paper before I start typing!
That has to suck. I hope you're properly avenged when you find work in a
savvier, respectful competitor and KICK THEIR ASSES!
-- Kim-Ee
On Sun, Apr 28, 2013 at 6:10 PM, Richard A. O'Keefe wrote:
>
> Damn! Why did Watts Humphrey have to die before he'd convinced
> the world that the cheapest way to fix bugs is to keep them out
> in the first place?
I think that much has to do with the historical division in computer
science. We
On 29/04/2013, at 3:26 AM, Chris Smith wrote:
> I think it's worth backing up here, and remembering the original point
> of the proposal, by thinking about what is and isn't a goal. I think
> I'd classify things like this:
>
> Goals:
> - Use a lightweight, common, and familiar core syntax for s
I think it's worth backing up here, and remembering the original point
of the proposal, by thinking about what is and isn't a goal. I think
I'd classify things like this:
Goals:
- Use a lightweight, common, and familiar core syntax for simple formatting.
- Still allow haddock-specific stuff like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/04/13 11:57, Joe Nash wrote:
> On 28 Apr 2013 11:33, "Mateusz Kowalczyk"
> wrote:
>>>
>>> If the flexibility of having it pandoc compatible is a desired
>>> feature, can this not be achieved through implementing markdown
>>> for haddock as wel
On 28 Apr 2013 11:33, "Mateusz Kowalczyk" wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 28/04/13 00:08, Joe Nash wrote:
> > Managed not to send to all:
> >
> > I think the reason markdown was the original suggestion was due to
> > the fact it is a very widespread and popular sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/04/13 00:08, Joe Nash wrote:
> Managed not to send to all:
>
> I think the reason markdown was the original suggestion was due to
> the fact it is a very widespread and popular syntax, and as Johan
> commented in the original thread, has to an e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/04/13 22:18, John MacFarlane wrote:
> I agree with Chris that it would be better to have a standard
> syntax for Haskell documentation. Especially if the alternative is
> ten different markup languages. (Remember, all of these need to be
> suppo
I agree with Chris that it would be better to have a standard syntax for
Haskell documentation. Especially if the alternative is ten different
markup languages. (Remember, all of these need to be supported in
haddock, which is a basic piece of infrastructure.)
Here's a thought. Instead of adding
On Sat, Apr 27, 2013 at 1:47 PM, Ben wrote:
> asciidoc has been mentioned a few times in comments, i think it's worth
> looking at.
>
This is the problem I was afraid of: for every markup syntax under the sun,
someone will come along to champion it.
The choice of one or N syntaxes is ultimately
asciidoc has been mentioned a few times in comments, i think it's worth looking
at.
* mature, over 10 years old (predates markdown i think), not "just another
markdown clone"
* human readable, but it has a lot of advanced features including mathematical
formulas.
* github supports it (they
Oops, forgot to reply all.
-- Forwarded message --
From: "Chris Smith"
Date: Apr 27, 2013 12:04 PM
Subject: Re: [Haskell-cafe] Markdown extension for Haddock as a GSoC project
To: "Bryan O'Sullivan"
Cc:
I don't agree with this at all. Far more i
On Sat, Apr 27, 2013 at 2:23 AM, Alistair Bayley wrote:
> How's about Creole?
> http://wikicreole.org/
>
> Found it via this:
>
> http://www.wilfred.me.uk/blog/2012/07/30/why-markdown-is-not-my-favourite-language/
>
> If you go with Markdown, I vote for one of the Pandoc implementations,
> probabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/04/13 10:23, Alistair Bayley wrote:
> How's about Creole? http://wikicreole.org/
>
> Found it via this:
> http://www.wilfred.me.uk/blog/2012/07/30/why-markdown-is-not-my-favourite-language/
>
> If you go with Markdown, I vote for one of the Pa
How's about Creole?
http://wikicreole.org/
Found it via this:
http://www.wilfred.me.uk/blog/2012/07/30/why-markdown-is-not-my-favourite-language/
If you go with Markdown, I vote for one of the Pandoc implementations,
probably Pandoc (strict):
http://johnmacfarlane.net/babelmark2/
(at least then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings,
In light of fairly recent discussion, on this mailing list, I decided
to investigate the topic of Markdown support for Haddock. The archives
of the recent discussion can be seen at [1]. This post aims to
summarise the current state of discu
31 matches
Mail list logo
