= Description =

I love the new {{{"."}}} bulletless list mark up.  However, I noticed that if you have a relative wiki link near the list that the parser get's confused.

== Steps to reproduce ==
## Describe the steps needed to reproduce the bug. If we can't reproduce it, we  probably can't fix it.
Consider this wiki mark up
{{{
 . List Item
   . Indented Item
   . Another Indented Item

 ../SeeMoreExamples
}}}

  . List Item
   . Indented Item
   . Another Indented Item

 ../SeeMoreExamples


The {{{../SeeMoreExamples}}} should show up as a link and instead is considered part of the list (removing the leading dot).

== Details ==

This Wiki (feature added with 1.5.2 release)


== Workaround ==
## How to deal with the bug until it is fixed
The marked I used before is the work around.  Force the link into the extended link syntax {{{["../SeeMoreExamples"]}}}

= Discussion =
This is expected. You also can't begin an itemized list item with a "*".

 Well, not expected, or I wouldn't have reported it as a defect.  This link worked prior to upgrading to 1.5.2.

 The point was that above wasn't considered a list item before, it is a link 

But now that you point that out I don't believe the my star'ed sentence should render as it does
 **Don't Mark this UP**

The documentation HelpOnLists, states that a space must preceded and follow the mark up {{{"**"}}} does not follow that.

This is a markup regression, severe IMHO. -- AlexanderSchremmer <<DateTime(2006-02-08T22:33:49Z)>>

Again: this is not a bug, it works as designed. If you want it to work different, make a better proposal. BTW: If we enforce that blank following, others will complain "this worked before", so what!?

 This does not work as designed, a wrong link is rendered. The solution is to swap the both regular expression lines in the parser. -- AlexanderSchremmer <<DateTime(2006-02-09T08:43:06Z)>>

  Just moving word_rule up does not work. So if you have a "solution", why don't you commit it?

= Plan =
## This part is for Moin``Moin developers:

 * Priority: 
 * Assigned to:
 * Status: seems to be fixed in current 1.5.8

----
## If you are a moin core developer, replace the category to Category* in these cases:
## Category MoinMoinNoBug - if this is not a bug.
## Category MoinMoinBugConfirmed - if you can confirm the bug on current code.
## Category MoinMoinBugFixed - after the bug is fixed in current code.

CategoryMoinMoinBug