Skip to content
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

Ambiguity in spec between setext header and list with empty second item #95

Closed
nate-red opened this issue Sep 8, 2014 · 1 comment
Closed
Labels

Comments

@nate-red
Copy link

nate-red commented Sep 8, 2014

I have virtually no idea about the technicalities of the project, but I want to report what seems to be a bug:

if you input:

- This text shouldn't be bold
  -

with two spaces before the second "-", the text will be shown as big, bold letters.

I don't think this is normal,

thanks.

@jgm
Copy link
Member

jgm commented Sep 8, 2014

What's going on is that the contents of the first list item
are a valid setext header, according to the spec. (The
setext underline can be just one character long.)

However, there is an ambiguity between this interpretation
and an interpretation as a sublist with an empty item that
needs to be addressed in the spec.

@jgm jgm changed the title Bug ? Ambiguity in spec between setext header and list with empty second item Oct 24, 2014
@jgm jgm added the spec label Oct 24, 2014
@jgm jgm closed this as completed in 4cae33a Dec 28, 2014
jgm added a commit that referenced this issue Jul 12, 2021
These said that a single `-` that could be interpreted as
either an empty list item or a setext header underline
should have the latter interpretation.  But now that the
spec says that an empty list item can't interrupt a paragraph,
this is unnecessary.

See commonmark/commonmark.js#222.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants