Inline container precedence with attributes about djot

[jgm]

The rules you're quoting are said to cover "precedence for inline containers." The way I was thinking of it, that excludes things like code spans and attributes. These have precedence over inline containers. In a full spec, all of this would need to be spelled out more explicitly.

Maybe the other issue is now fixed? With the latest in main I'm getting:

% ./djot 
*{a=[txt](url)
<p>*{a=<a href="url">txt</a></p>

[hellux]

The rules you're quoting are said to cover "precedence for inline containers." The way I was thinking of it, that excludes things like code spans and attributes. These have precedence over inline containers. In a full spec, all of this would need to be spelled out more explicitly.

Yes, and this precedence is probably the better alternative, but it does requires backtracking to parse. You have to parse for attributes first, and if it fails you have to go back and parse everything again. But I guess it should still be parsable in linear time, it is not really possible to nest arbitrarily many attributes within each other (trying to open another quote/comment will close the previous one).

Maybe the other issue is now fixed? With the latest in main I'm getting:

% ./djot 
*{a=[txt](url)
<p>*{a=<a href="url">txt</a></p>

I think I accidentally typed the example without quotes. With quotes it still parses as text on the main branch:

% ./djot
*{a="[txt](url)
<p>*{a=&ldquo;[txt](url)</p>