aboutsummaryrefslogtreecommitdiff
path: root/spec.txt
AgeCommit message (Collapse)Author
2017-07-31clarify that backslash escaped `*` or `_` may precede or follow a delimiter ↵Aidan Woods
run of `*` or `_` respectively
2017-06-29Added another illustrative case for code spans.John MacFarlane
Closes jgm/CommonMark#463.
2017-06-29Removed possibly misleading 'either's.John MacFarlane
These are sometimes interpreted as XOR (and that isn't meant in this case). Closes jgm/CommonMark#467.
2017-06-03Mention removing surrounding whitespace from link labelsMatthias Geier
2017-05-27Forgot a `.`Aidan Woods
2017-04-23Clarify that some blocks can contain "code spans"Matthias Geier
2017-04-12Clarify HTML blocks re: "nested" blocksYuki Izumi
2017-04-09Clarify precedence of thematic breakAidan Woods
There already exists the statement: "When both a thematic break and a list item are possible interpretations of a line, the thematic break takes precedence". This adjustment ensures that this precedence is achieved by the list item definition.
2017-04-05Fix typo and clarify expansionScottAbbey
I guess this would have passed a spell checker since *theses* is the plural of *thesis*. Listing the number of spaces the first tab is expanded into reduces the cognitive load required to figure out why the next line talks about six spaces.
2017-03-19Add fenced code block example with not enough backticks.Philipp Matthias Schaefer
2017-03-18Add a missing "iff"Matthias Geier
2017-03-16Acknowledge Aaron Swartz's role in developing Markdown.John MacFarlane
2017-03-05Example for disabling image markup: remove a backslashMatthias Geier
Escaping `[` disables the markup, escaping `!` on top of that doesn't change anything and is therefore misleading in this example.
2017-02-17 is a general category not a classPhilipp Matthias Schaefer
2017-01-08Change Rule 14 for Emphasis.John MacFarlane
Previously the nesting Strong (Emph (...)) was preferred over Emph (Strong (...)). This change makes Emph (Strong (...)) preferred. Note that the commonmark reference implementations were not entirely consistent about this rule, giving different results for ***hi*** and ***hi**** This change simplifies parsing. It goes against the majority of implementations, but only on something utterly trivial.
2016-12-01Allow unlimited balanced pairs of parentheses in link URLs.John MacFarlane
See #166. The rationale is that there are many URLs containing unescaped nested parentheses.
2016-11-18Bump verison to 0.27.John MacFarlane
2016-09-20Clarify that the exception only applies to first item in list.John MacFarlane
Closes #420.
2016-09-15Added cases clarifying precedence of shortcut links.John MacFarlane
Closes #427.
2016-09-14Merge pull request #422 from TimothyGu/unicode-whitespaceJohn MacFarlane
Add examples for Unicode whitespace
2016-09-12Added h2..h6 to block tag list.John MacFarlane
Closes #430.
2016-08-20Added closing paren. Fixes #428.John MacFarlane
2016-08-12Remove duplicated test.Maxim Dikun
Tests 390 and 391 are equal in 0.26.
2016-08-08Use fenced code blocks for markdown examples that are not test casesJohn MacFarlane
for uniformity.
2016-08-07Removed duplicate reference to "container block".John MacFarlane
2016-08-06Add examples for Unicode whitespaceTimothy Gu
In light of jgm/commonmark.js#107, add a few examples/test cases to make sure the distinction between Unicode whitespace and regular whitespace is kept.
2016-07-21Fix missing closing paren typoRobin Stocker
2016-07-20Update statement on blank lines and lists.Jesse Rosenthal
The definition of a list still said that "two blank lines end all containing lists." That rule has been removed.
2016-07-15Bump version to 0.26, update changelog.John MacFarlane
2016-07-13Merge pull request #417 from neongreen/patch-1John MacFarlane
Fix a typo in the spec
2016-07-13Moved restriction on paragraph-interrupting lists to list item specJohn MacFarlane
instead of list marker spec.
2016-07-13Empty list items cannot interrupt a paragraph.John MacFarlane
This removes an ambiguity between setext headers and lists in cases like foo -
2016-07-12Fix a typo in the specArtyom
2016-07-11Use <= instead of < for clarity.John MacFarlane
2016-07-11Removed the "two blank lines breaks out of lists" rule.John MacFarlane
This is incompatible with the principle of uniformity (and indeed with the spec for list items, which requires that the meaning of a chunk of lines not change when it is put into a list item.)
2016-07-11Ordered list markers that interrupt a paragraph must start with 1.John MacFarlane
2016-07-02Improved the section on tabs.John MacFarlane
Added some test cases for ATX headers and thematic breaks. Clarified that it's not just cases that affect indentation that matter, but all cases where whitespace matters for block structure.
2016-07-02Removed example of ATX header with tab after `#`.John MacFarlane
A tab ought to work; language at the beginning of the spec will be revised to make this clear.
2016-07-02Revert "Revert "Revert "ATX headers: clarify where tabs can go."""John MacFarlane
This reverts commit ee779cb7f8ea3c6274aef89f9916931b907e211e.
2016-07-02Revert "Clarified tab usage in thematic breaks."John MacFarlane
This reverts commit 5ca9ca1d5e70cbfe8eeae12f96e761c405ad8f86.
2016-07-01Merge pull request #412 from colinodell/patch-1John MacFarlane
Allow HTML blocks to end on the last line of their container
2016-06-27Revert "Revert "ATX headers: clarify where tabs can go.""John MacFarlane
This reverts commit 85bd3b9b149bef97755f16538e9c01cc386f6e5b.
2016-06-27Revert "ATX headers: clarify where tabs can go."John MacFarlane
This reverts commit ee75eb33f9bdf6901388e5f9175834acca814e5c.
2016-06-27ATX headers: clarify where tabs can go.John MacFarlane
See #410.
2016-06-27Allow HTML blocks to end on the last line of their containerColin O'Dell
See discussion here: https://github.com/jgm/commonmark.js/issues/103#issuecomment-228888648
2016-06-27Clarified tab usage in thematic breaks.John MacFarlane
Closes #410.
2016-06-25Make "softbreak" a link targetMatthias Geier
2016-06-24Spec changes in strong/emph parsing.John MacFarlane
See https://talk.commonmark.org/t/emphasis-strong-emphasis-corner-cases/2123 for motivation. This restores intuitive parsings for a number of changes. The main change is to disallow strong or emph when one of the delimiters is "internal" and the sum of the lengths of the enclosing delimiter runs is a multiple of 3. Thus, **foo*bar*** gets parsed `<strong>foo*bar</strong>` rather than `<em><em>foo</em>bar</em>**` as before.
2016-06-23Merge pull request #409 from xoofx/html_end_parsingJohn MacFarlane
Improve tests for HTML end block parsing
2016-06-23Add tests to check that markdown parsing is working fine after an HTML block ↵Alexandre Mutel
end tag
generated by cgit v1.2.3 (git 2.46.0) at 2025-07-16 16:43:45 +0000