-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Loose" Lists #1
Comments
vinnymac
pushed a commit
to vinnymac/marked
that referenced
this issue
Jul 20, 2016
Disable elements in InlineLexer as well
matt-
added a commit
that referenced
this issue
Jul 29, 2016
Optional semicolon in html entities regex
gibson042
pushed a commit
to gibson042/marked
that referenced
this issue
Oct 20, 2017
trim code after regexp
UziTech
pushed a commit
that referenced
this issue
Jul 13, 2020
mask reflinks in a separate function
5 tasks
zhenalexfan
pushed a commit
to zhenalexfan/MarkdownHan
that referenced
this issue
Nov 8, 2021
Demo versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When "loose" lists, as they're called (lists with their items separated by 2 line feeds), get implemented, it introduces some ambiguity to parsing. This is a bit of a problem with the markdown grammar itself.
What is that? Is it 2 separate lists? One tight, one loose? Is it three lists? One with 2 items, and 2 with one item? Is it a single list with the items spaced differently? The only solution I see, is to actually always separate consecutive lists by 3 line feeds:
Which would be rendered as 2 lists: one tight, one loose. This is probably what will happen once I merge the experimental branch.
The text was updated successfully, but these errors were encountered: