Laurenz

> Another currently (I think) unsolvable example. You might be aware, but you can reconstruct the heading from its body: ``` #show heading: block.with(stroke: 1pt, inset: 4pt) = Hello #show...

The problem is that you _do_ want to retain the show rule for nested content not generated by the rule (consider list show rules on a list in a list)....

No no, don't worry. It's good to see ideas thrown around, I was just pointing out a possible problem with the approach to add to the discussion.

The current plan is to add `revoke` rules, which take a selector and disable one or multiple rules based on that, e.g.: ```typ #show raw: "nope" #revoke raw `Default` ```...

> Will code only be able to revoke rules from its own scope or can it revoke ancestral rules too? Also ancestral rules. > In the case of two rules...

> I just want to point out that now you have to juggle 4 keywords, which are all different. I feel like the apply, if will be added, should have...

Note that the idea was only to replace `show: x` with `apply x` not `show x: y`.

The design on this feature is not yet finalized because there wasn't consensus on what it should and shouldn't do, so it will likely still take a while. The latest...

> If I understand it correctly, stack size is pretty big (second argument) ... This stack size applies to the compiler itself, not the WASM plugin executor. I'm honestly not...

This will indeed break introspection in math, e.g.: ```typ $ #metadata("hi") $ #context query(metadata) ``` To fix it properly, MetaElem::data probably needs to be handled in better non-frame way by...