ecmarkup
ecmarkup copied to clipboard
tc39
An HTML superset/Markdown subset source format for ECMAScript and related specifications
The lines: ``` /a[a-z]{2,4}?/.exec("abcdefghi") /(aa|aabaac|ba|b|c)*/.exec("aabaac") /(z)((a+)?(b+)?(c))*/.exec("zaacbbbcac") /(a*)*/.exec("b") /(a*)b\1+/.exec("baaaac") ``` are highlighted oddly, because the `...` markup is surrounding the wrong text. In contrast, the line: ```"aaaaaaaaaa,aaaaaaaaaaaaaaa".replace(/^(a+)\1*,\1+$/,"$1")``` has the regex correctly...
Per [IRC discussion](http://logs.libuv.org/tc39/2018-02-22#23:16:22.320). `ecmarkup spec.html out/index.html --assets inline --copyright true`, without `--contributors "…"`, cannot generate a copyright and license notice. But it currently outputs a spec file silently and successfully,...
I can't imagine a use case for a variable which appears only once, and this would have caught a recent typo in one of my proposals.
`href` attributes do not allow URIs with the "data" scheme because [the CLI sets `fetch` to a thin wrapper around `fs.readFile`](https://github.com/bterlson/ecmarkup/blob/49471301cdb02fbff2c999c655110f1a1164a483/src/cli.ts#L25). It would be convenient and expected for such values...
It'd be great if when the input file was not changed, the "updated at" date could remain the same - for example, when I've merely updated the deps, and want...
For the purposes of allowing web specs (written in Bikeshed, or written in something that obeys the Bikeshed [definition contract](https://github.com/tabatkins/bikeshed/blob/master/docs/dfn-contract.md)) to more easily reference Ecmarkup specs, it would be good...
For a while now I've been maintaining [emu-algify](https://www.npmjs.com/package/emu-algify), which reaches into the internals of Ecmarkup in order to add ES-style EMD processing and EMU autolinking to https://streams.spec.whatwg.org/. Right now it's...
``` html global1.Zone.current; // succeeds global2.Zone.current; // throws: currentRealm = realm1; thisRealm = functionRealm = realm2 const getter1 = Object.getOwnPropertyDescriptor(global1.Zone, "current").get; const getter2 = Object.getOwnPropertyDescriptor(global2.Zone, "current").get; getter1.call(global2.Zone); // throws: currentRealm...
 
For example the current spec has "The _TypedArray_ Constructors"