ecmarkdown
ecmarkdown copied to clipboard
tc39
A shorthand language for writing ECMAScript-style algorithms, inspired by Markdown
Line breaks in list items contents are preserved in output, but the indenting white space following them should be stripped. This will improve the rendering sought by https://github.com/tc39/ecmarkup/pull/513 . **Exaggerated...
We should handle Windows line endings somehow, either by explicitly supporting them in input (though presumably outputting them as just `'\n'`) or (my preference) explicitly disallowing them, with a useful...
Like http://spec.commonmark.org/dingus/ basically. I can do this.
``` * foo * bar ``` will throw a parse error because the bar list item is dedented past the origin list item.
Tag tokens are appended to text nodes. Seems like the emitter should get to handle tags separately from text so we should fix this.
I hear @rwaldron wants a link syntax nicer than ``. Let's figure that out. Directly borrowing CommonMark link syntax has a few problems in my opinion. In order from worst...
I'm on the fence ... seems like potentially more trouble than they're worth. But maybe it's OK, given that any other usage of ' and " should be inside code...
In the latest draft Allen updated the convention for "List literals" to use «x» instead of (x). To make this easier to type we might want to let people type...
http://people.mozilla.org/~jorendorff/es6-draft.html#sec-ecmascript-language-types-number-type makes the case that **NaN** is produced by the program expression `NaN`. Is this distinction really useful? Or could we use `NaN` everywhere? (Similarly `0`, `+Infinity`, `TypeError`, etc.) If...
I.e. does combining code, variables, and values behave as expected?