On Tue, Mar 4, 2008 at 10:08 PM, Michel Fortin
[EMAIL PROTECTED] wrote:
Le 2008-03-04 à 13:15, david parsons a écrit :
But what's the intent of ***hello*, sailor** ?
Should it produce
1. strongemhello/em, sailor/strong
2. strong*hello*, sailor/strong
3.
Michel Fortin wrote:
Le 2008-03-04 à 21:47, Seumas Mac Uilleachan a écrit :
david parsons wrote:
And how about _cut here_ ?
This is a problem. Anything more than 4 _ per side does not render
but with 4 it does (in PHP) if you have cut here are you
expecting it to
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
In article [EMAIL PROTECTED],
Seumas Mac Uilleachan markdown-discuss@six.pairlist.net wrote:
Currently (which is strange)
the first line in my example has three spaces and is a first level list.
The next line has only two but becomes a **second level** list.
I believe that the markdown
A list item's parent is the most recent list item whose bullet is indented
less than its own. If there's no such parent, then the item belongs to a
root-level list.
http://six.pairlist.net/pipermail/markdown-discuss/2008-March/001076.html
Is there any case where this doesn't do the right
My only other concern is when stepping back out of the nesting.
Suppose we have the following list:
* no spaces - level 1
* 4 spaces - level 2
* 6 spaces - level 3
* 2 spaces - level 1.5 ???
Obviously, that would break. But what's the best way to handle that? I
do *not*
1. Item one
2. Item two
. Item three
. Item four
. Item five
But that's not very readable, is it?
Note the word optional in the paragraph preceding this example. I
think markdown's ideal of allowing the source to be readable should be
understood as making possible and easy for
In article [EMAIL PROTECTED],
John Fraser markdown-discuss@six.pairlist.net wrote:
A list item's parent is the most recent list item whose bullet is
indented less than its own. If there's no such parent, then the item
belongs to a root-level list.
On 5 Mar 2008, at 05:02, Michel Fortin wrote:
[big explanation]
So you're basically using a line by line approach.
Yes, seeing how the block-level nesting stuff affects things “line by
line”, this seems like the best approach :)
I was thinking about that as a possibility for parsing
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
In article [EMAIL PROTECTED],
John Fraser markdown-discuss@six.pairlist.net wrote:
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
* [EMAIL PROTECTED] [EMAIL PROTECTED] [2008-03-03 23:45]:
Is it possible for everyone to agree in all cases about how
the user’s intent should be teased out? Clearly it is
conceivable that enough effort could be made to write all
agreements down.
And if you write down what intent
* Michel Fortin [EMAIL PROTECTED] [2008-03-05 05:10]:
A better question is what to do with this:
*hello **dear* boy**
That’s a very good question. Here’s a counterquestion: what does
a human reader see in that text? Based on the visual apperance I
think I would make it translate to this:
14 matches
Mail list logo
