Laurenz

The problem is that this will ignore counter updates. Try putting `counter(heading).update(1)` somewhere in between the headings. The output will be different between PDF and `#outline()`.

That probably works quite often, but is too brittle in my opinion. I think we should aim for a proper solution, which will likely involve a synthesized field, as said...

It was an intentional design decision that a package only exposes its definitions and not its directory tree. Otherwise, pretty much any change to a package would be potentially breaking....

What I like about the current setup is that the internal package organization is very flexible. Assuming we had better syntax to allow something like the following: ```typ #import "@local/templates:0.1.0":...

Okay, I think we can make this a thing!

I would say, it should definitely be the former, because if you want the latter you can just write `#import "@local/templates:0.1.0": slides`.

On the parser side, you've found the right place. You would also need adjustments in `ast.rs` and maybe `kind.rs` on the syntax side. On the evaluation side, the relevant code...

Yeah, `none` and `auto` are a bit special because they are the only values of their type, their type isn't actual bound to any name. You'd rarely need it because...

As @LuxxxLucy pointed out, we first need to define how highlight should behave in the first place. I _think_ the most reasonable thing would be to highlight the whole equation...

While it may seem somewhat weird, it is consistent with how things generally work, so I would refrain from adding more special cases.