Markdown: When paragraph starts with * it is (falsely) treated as a list

[daviwil]

From @uliska on April 3, 2016 9:3

This is related to #4 but I'd say it's an issue of its own.

When a paragraph starts with a * * highlighting reflowing turns it into a list with arbitrary list items:

*Note:* This is a very long paragraph that starts with a highlighted word. But it is not a list

=>
*Note:* This is a very long paragraph that
*starts with a highlighted word. But
*it is not a list

However, this isn't even rendered as a list but as a paragraph with interspersed asterisks.

Suggestion: To be interpreted as a list there has to be whitespace after the leading asterisk.

Copied from original issue: atom/autoflow#46

[daviwil]

From @uliska on April 3, 2016 9:30

Update: The same is true when the paragraph starts with a ** highlighting:

**Summary:**   Whenever you see an expression wrapped in parentheses you know
**that it is a list whose first element should be a procedure, which is then
**applied to all remaining list elements *(note that there is the concept of

Which causes even stranger results

[daviwil]

From @cwensel on April 20, 2016 23:3

would be great if this line was configurable, so '*' could be excluded

linePrefix = block.match(/^\s*[\/#*-]*\s*/g)[0]

[stale]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. Because the Atom team treats their issues as their backlog, stale issues are closed. If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of Atom
2. Comment that the issue is still reproducible and include:
   • What version of Atom you reproduced the issue on
   • What OS and version you reproduced the issue on
   • What steps you followed to reproduce the issue

Issues that are labeled as triaged will not be automatically marked as stale.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!