00:31:21  * jwaldenjoined
01:17:01  * Jayfluxquit (Quit: Leaving)
01:23:16  * AtumTquit (Remote host closed the connection)
01:23:21  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
01:44:15  * not-an-aardvarkjoined
02:10:31  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
04:46:17  * caridyjoined
04:50:01  * caridyquit (Remote host closed the connection)
06:10:52  * jmdyck1quit (Remote host closed the connection)
06:13:18  * jwaldenquit (Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805])
06:23:21  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
10:39:13  * gskachkovquit (Quit: gskachkov)
10:40:06  * gskachkovjoined
11:25:10  * mylesborinsquit (Quit: farewell for now)
11:25:41  * mylesborinsjoined
11:34:40  * gskachkovquit (Quit: gskachkov)
11:35:22  * gskachkovjoined
12:28:59  * gsathyaquit
12:29:16  * gsathyajoined
13:08:55  * jmdyckjoined
13:12:56  * AtumTjoined
13:14:16  * keith_millerjoined
13:22:41  * gibson042joined
13:34:41  * gibson042quit (Ping timeout: 256 seconds)
14:52:08  * AtumT_joined
14:55:24  * AtumTquit (Ping timeout: 256 seconds)
15:05:26  * AtumTjoined
15:06:26  * AtumT_quit (Ping timeout: 255 seconds)
15:25:14  * bradleymeckjoined
15:35:17  * bradleymeckquit (Quit: )
16:24:21  * jschoijoined
16:25:58  <jschoi>Hi, everyone. I’m writing a formal specification for https://github.com/tc39/proposal-pipeline-operator/wiki#proposal-4-smart-mix. Is this a good place to ask questions about working with Ecmarkup?
16:44:05  <littledan>jschoi: Yes it is!
16:44:09  <littledan>ask away
17:05:14  <jschoi>Thanks! I’m trying to use Ecmarkdown in an <emu-intro> element, but the ecmarkup command isn’t recognizing the markdown. From what I can tell, Ecmarkup’s documentation does suggest that Ecmarkdown should be usable in <emu-intro>…but maybe I’m misunderstanding it. Is there something special I need to do to the <emu-intro>, or is Ecmarkdown only ever supported in algorithms?
17:05:50  <Domenic>You might need a linebreak so that the markdown and the open/close tags appear on separate lines; did you try that already?
17:07:54  <jschoi>@Domenic: Thanks for the reply; yes, I’ve already tried separate lines between tags and Markdown content.
17:08:20  <Domenic>OK, yeah, that's the only legit issue I could imagine; at this point it's more likely a bug...
17:10:00  <jschoi>https://github.com/js-choi/proposal-smart-pipelines/blob/bbb9a1fa3cb314a340fa1afb2992d9af03cc648d/spec.html
17:10:43  <jschoi>Right now, `ecmarkup spec.html` is complaining, “Error: Couldn’t find title for clause #introduction”.
17:18:46  <jschoi>@littledan: Left a reply to your comment at https://github.com/tc39/proposal-pipeline-operator/issues/89#issuecomment-364673083. Basically, I’m not trying to use Grammardown or grammar productions; I’m trying to use Ecmarkdown for paragraph content.
17:19:45  <littledan>jschoi: I always use h1 for all headings in ecmarkup. Does that work for you?
17:20:14  <littledan>I also use ul/li for lists. My understanding was that ecmarkdown was a thing for <emu-alg> tags
17:21:54  <jschoi>Yeah, if Ecmarkdown is not intended for use in anything other than algorithms, then I’ll just write HTML for paragraph content. I was confused by the mentioning of “Ecmarkdown syntax for both paragraphs and algorithms” in https://bterlson.github.io/ecmarkup/#intro.
17:23:17  <jmdyck>The spec certainly uses ecmarkdown outside of emu-alg elements.
17:27:00  <jmdyck>Offhand, I'm not sure if there's any content-text that isn't subject to ecmarkdown-processing. Maybe code samples?
17:29:35  <jmdyck>Oh, and <emu-grammar> elements, of course.
17:32:54  <littledan>jmdyck: Does it support # in place of h1?
17:33:11  <jmdyck>don't think so
17:34:08  <jmdyck>Oh, wait, I guess it does.
17:34:32  <jmdyck>But the spec doesn't use that feature.
17:35:45  <littledan>I wonder why jschoi is running into this problem then
17:36:58  <jmdyck>when you run a doc through ecmarkup, the ecmarkdown processing you get might be different from if you ran it through ecmarkdown directly.
18:01:28  <jschoi>For what it’s worth, `ecmarkup` no longer complains if the `#` heading block in https://github.com/js-choi/proposal-smart-pipelines/blob/bbb9a1fa3cb314a340fa1afb2992d9af03cc648d/spec.html is removed, but it also still does not interpret the paragraph below it as Ecmarkdown.
18:53:27  * gskachkovquit (Ping timeout: 240 seconds)
19:05:05  * not-an-aardvarkjoined
19:23:45  * gskachkovjoined
19:34:45  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
19:52:45  * keith_millerjoined
21:37:36  * Draggorquit (*.net *.split)
21:37:37  * FireFlyquit (*.net *.split)
21:37:39  * fletquit (*.net *.split)
21:38:15  * maggiepintquit (*.net *.split)
21:38:15  * mathiasbynensquit (*.net *.split)
21:38:15  * thejameskylequit (*.net *.split)
21:38:16  * ChanServquit (*.net *.split)
21:42:15  * ChanServjoined
21:42:15  * maggiepintjoined
21:42:15  * mathiasbynensjoined
21:42:15  * thejameskylejoined
21:45:23  * Draggorjoined
21:45:24  * FireFlyjoined
21:45:24  * fletjoined
21:45:27  * M-IvanSanchezquit (Ping timeout: 260 seconds)
22:17:45  * keith_millerquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
22:21:32  * keith_millerjoined
22:25:27  <littledan>jschoi: Does it work if you use <h1> as a workaround?
22:43:27  <jschoi>littledan: Ah, no, it does not. Using an <h1> element followed by a bare Markdown paragraph causes the document to be generated with that paragraph as unprocessed Markdown.
22:44:31  <littledan>well, one way to write specification text (how I usually do it) is HTML in most sections, and markdown in algorithms. Maybe this could work for you, even if it's uglier
22:45:46  <jschoi>Yeah, it’s annoying because I’m trying to have the introduction match stuff from the repository readme, but what can you do.
22:46:47  <jschoi>littledan: Incidentally, I’m wondering if # might be an option for nullary pipe placeholder; visual noise aside, would it actually be syntactically ambiguous with `.#` private fields? After all, a pipe placeholder can never occur after a `.`.
22:46:49  <littledan>what I usually do is have the introduction just point to the readme, so there's nothing to keep in sync
22:47:06  <jschoi>Yeah.
22:47:37  <littledan>jschoi: I don't think there's any syntactic ambiguity, but as far as intuition, I can see how people would want to avoid reusing # as it already has another meaning
22:47:44  <littledan>of course, so does ?, so that's not really a tiebreaker
22:48:26  <littledan>even if we adopt wycats's private shorthand syntax, there would still not be any ambiguity since that has to be followed by an IdentifierName
22:48:39  <jschoi>Right.
23:05:31  * M-IvanSanchezjoined
23:22:44  * Bakkotquit (Quit: death)