PgBiel
PgBiel
> #import "set.typ" is certainly not good though as it won't be accessible. I think that's wrong: I can access it transitively from another module. For example: ```typ // set.typ...
> However, the module represented by the *current file* having a member `set` that can only be accessed from *outside the current file* feels very wrong. At least in my...
I think the ship has already sailed for keyword bindings (consider the built-in `selector.and` for example), so I'd say the alternative of eventually adding some raw identifier syntax is better...
Drafting as I'll take a stab at not using decimals for int rounding.
We discussed this a bit over Discord: Grids do have header and footer orphan prevention, in the sense that it won't let the header and footer be the only rows...
cc @EpicEricEE I wonder if #6335 would fix this? (Tested on #6168 and it still happens there)
Prior discussion: https://github.com/typst/typst/pull/4227#issuecomment-2140218562 I wonder if it would make more sense to retain the original idea of being able to map one namespace to one path. Would love to hear...
Drafting until further discussion.
Would it be too expensive to have one counter per grid / table? And then you'd be able to `.final()` if you need to find the last (relative) page /...
I agree continuation handling is important - repetition by itself is already handy for certain use cases, but that can be reproduced in pure Typst fairly easily. Do we have...