Oops, I just realized I've been missing about half of the messages on
Markdown-discuss ever since I switched servers last week. Should be
fixed now.
But Michel, I'm sorry I missed this:
http://six.pairlist.net/pipermail/markdown-discuss/2008-March/001230.html
As I told Tom, I'd like a
On Mar 25, 2008, at 6:48 PM, Milian Wolff wrote:
Am Dienstag, 25. März 2008 schrieb John Fraser:
I've built a quick-and-dirty diff GUI for Babelmark (thanks,
Michel!). You can get it as a bookmarklet here:
http://attacklab.net/babelmark/
Great, what about grouping by output? So that one can
On Mar 4, 2008, at 11:09 PM, Michel Fortin wrote:
Yeah, the list implementation in Markdown.pl and PHP Markdown
doesn't follow the at all the little of a spec we have now. I've
been thinking about rewriting the list parser in PHP Markdown, but
I'm wondering what to do to not suddenly change
On Mar 5, 2008, at 2:40 PM, Waylan Limberg wrote:
On Wed, Mar 5, 2008 at 1:46 PM, Vinay Augustine [EMAIL PROTECTED]
wrote:
* no spaces - level 1
* 4 spaces - level 2
* 6 spaces - level 3
* 2 spaces - level 1.5 ???
With the rule just proposed, wouldn't the last line simply be
On Mar 5, 2008, at 2:38 PM, david parsons wrote:
When I write a really long list,
* sometimes, after a particularly long and
detailed list item, I'll lose track of the
exact indentation and
* add one too many spaces to the leading
indent.
so it would be bad if
it gets confused, we'd need to
define all the corner cases completely -- or risk locking users into a
particular reading of the spec.
I'm all for writing a specification, but I think its purpose should be
to inform and to justify a reference implementation and test suite.
- John Fraser
in this approach, I'll try to do a quick hand-wavy
prototype next week to show what I'm talking about.
John Fraser
http://wmd-editor.com/ (going open source soon)
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net
to process the fixed TextMate manual on your computer.
John Fraser
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
to
JavaScript. I'd originally planned to write a Markdown parser from
scratch, but quickly realized it would be impossible to get 100%
compatibility without doing a direct, line-by-line port. And that's a
bad sign.
John Fraser
___
Markdown-Discuss mailing list
to I mean that it's a descendant of that node -- not a
sibling. So item 10 is part of the list that's nested within item 1.
John Fraser
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown
the board.
-John
On 3/5/07, A. Pagaltzis [EMAIL PROTECTED] wrote:
Hi John,
* John Fraser [EMAIL PROTECTED] [2007-03-05 15:35]:
On 3/5/07, A. Pagaltzis [EMAIL PROTECTED] wrote:
I've come to appreciate the fact that it means you can pump
the output of Markdown back through Markdown without
11 matches
Mail list logo
