Hi, I'm getting what I believe to be a bug. If I put the following in markdown: 1. This is a numbered list 2. Blah 9. This is another list item 10. Ok, weird bug here 11. It's really bothering me And when I run it through markdown.pl 1.01 I get out the following: <ol> <li>This is a numbered list</li> <li>Blah</li> <li>This is another list item <ol> <li>Ok, weird bug here</li> <li>It's really bothering me</li> </ol></li> </ol> Interestingly, I don't get this from the [python markdown][1], instead getting one list, as desired. Anyone know what's up? Or has this already been fixed? -Jacob [1]: http://www.freewisdom.org/projects/python-markdown/
I'm guessing it's because you have different indent levels. Try removing the spaces before 1-9. On 7/7/06, Jacob Rus <jrus@hcs.harvard.edu> wrote:> Hi, > > I'm getting what I believe to be a bug. If I put the following in markdown: > > 1. This is a numbered list > 2. Blah > 9. This is another list item > 10. Ok, weird bug here > 11. It's really bothering me > > And when I run it through markdown.pl 1.01 I get out the following: > > <ol> > <li>This is a numbered list</li> > <li>Blah</li> > <li>This is another list item > <ol> > <li>Ok, weird bug here</li> > <li>It's really bothering me</li> > </ol></li> > </ol> > > Interestingly, I don't get this from the [python markdown][1], instead > getting one list, as desired. > > Anyone know what's up? Or has this already been fixed? > > -Jacob > > [1]: http://www.freewisdom.org/projects/python-markdown/ > > _______________________________________________ > Markdown-Discuss mailing list > Markdown-Discuss@six.pairlist.net > http://six.pairlist.net/mailman/listinfo/markdown-discuss >
Hi John, * John Gruber <gruber@fedora.net> [2006-07-20 21:45]:> A. Pagaltzis <pagaltzis@gmx.de> wrote on 7/13/06 at 5:45 AM: > >So I would argue that there is room to tweak the indentation > >rules, but none to tweak the numbering requirements. I would > >instead suggest that to start a nested list, the marker be > >required to be indented at least three spaces more than the > >preceeding item. > > I agree. Why three though?to be conservative. Requiring three spaces is a slightly smaller change of the newly documented behaviour than four, compared to the existing undocumented one that someone out there *might* have relied on.> It "feels" like a reasonable number, but four spaces is the > magic cut-off point in all the other places where indentation > matters in Markdown.Yes, in terms of clarity of rules I would prefer requiring four. Since I can only make suggestions, I picked a conservative one. (I admit I should have specified my reasoning further.) If you as the one who makes the final call decree that four is the right number, I?ll be glad about that decision. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>