Parsing the contents of `inline block` and tables

[alco]

This does not produce a proper table

Built-in type         | Defined as
:-------------------- | :---------
`term`                | `any`
`binary`              | `one | two`
`bitstring`           | `three`

because of the pipe inside an inline block. Is it really "specified" by the "spec" (whichever "spec" defines table syntax) to act that way?

Intuitively, it is more appropriate to strip any symbols inside and of any special meaning, similar to how *, _, and others work.

[pragdave]

Escape the pipe with a backslash.
On Jul 20, 2014 3:44 AM, "Alexei Sholik" notifications@github.com wrote:

This does not produce a proper table

Built-in type	Defined as
term	any
binary	`one
bitstring	three

because of the pipe inside an inline block. Is it really "specified" by
the "spec" (whichever "spec" defines table syntax) to act that way?

Intuitively, it is more appropriate to strip any symbols inside and of
any special meaning, similar to how *, _, and others work.

—
Reply to this email directly or view it on GitHub
#2.

[alco]

Did that:

<table>
<colgroup>
<col align="left">
<col align="left">
</colgroup>
<thead>
<tr>
<th>Built-in type</th><th>Defined as</th>
</tr>
</thead>
<tr>
<td><code class="inline">term</code></td><td><code class="inline">any</code></td>
</tr>
</table>
<p><code class="inline">binary</code>              | <code class="inline">one \| two</code>
<code class="inline">bitstring</code>           | <code class="inline">three</code></p>

[pragdave]

Oops, you're right. I updated that in IO/ANSI/Docs but not earmark.

I just pushed 1.5 that fixes it.

On Sun, Jul 20, 2014 at 8:14 AM, Alexei Sholik notifications@github.com
wrote:

Did that:

Built-in type	Defined as
term	any

binary | one | twobitstring | three

—
Reply to this email directly or view it on GitHub
#2 (comment).