| 00:05 | <bakkot> | jschoi: in a proposal, or in the spec? |
| 00:07 | <jmdyck> | must be a proposal, if there's an <emu-grammar> on line 138 |
| 00:07 | <bakkot> | fair point |
| 00:10 | <bakkot> | jschoi: that warning is designed for the full spec, where the full grammar is available; I guess I did not properly disable it in proposals. so the problem is that ecmarkup does not know about that production because the proposal doesn't define it. I'll fix the suppression at some point; in the mean time, just ignore the warning, it'll still build |
| 00:12 | <jmdyck> | So there isn't a way for a proposal doc to include/import definitions from the spec? |
| 00:13 | <bakkot> | Short of copy-pasting, no |
| 00:13 | <bakkot> | at some point I mean to put that sort of thing into the biblio and also make the bilio updatable, but I haven't done so yet |
| 00:13 | <jmdyck> | So what's in the biblio file currently? |
| 00:15 | <bakkot> | It's basically a list of all AOs, which is used to generate the automatic xrefs in proposals |
| 00:15 | <bakkot> | (AOs and their #ids, I should say, as well as a couple other things.) |
| 00:15 | <jmdyck> | ok thanks |
| 00:17 | <bakkot> | but it hasn't been updated since ES6, which is no good; see https://github.com/tc39/ecmarkup/issues/251 also there's a bunch more information we could usefully include now; see https://github.com/tc39/ecmarkup/issues/316 |
| 00:19 | <bakkot> | (it does actually have a list of productions currently, but not what's actually in the productions, which is the thing this rule needs) |
| 02:25 | <jschoi> | bakkot: Thanks for explaining. Ah, I also see https://github.com/tc39/ecmarkup/issues/366 now; great. |