Enivex

@naim94a @emilyyyylime

It doesn't seem related to the actual number `0.65em`, because even `#show math.equation: set block(spacing: 0em)` will trigger it. Edit: Specifically, it's triggered whenever spacing is **less** than the default...

I would go a step further and move many of the text parameters into font. Especially things like stylistic sets, which doesn't make sense as a global setting for all...

Are you sure the fonts you are specifying are being used? Use `fallback: false` when investigating things like this

> But i think 10^n % 2 can never be zero... $10^n$ is divisible by $2$ for every $n \geq 1$, since $10 = 2 \cdot 5$ is.

> Should we maybe try to get rid of that thin line everywhere then? I feel like this is a rounding issue, so the question is whether it's on typst...

This can already be achieved by wrapping the image in a block with negative inset and clip: true

There's some discussion here https://github.com/tonsky/FiraCode/issues/854 Seems like the main motivation is to have ligatures enabled by default.

``` #set heading(numbering: (..it) => { it = it.pos() numbering("A.A",..if it.len() > 1 {it.slice(1)} else {()}) }) = Hello == sub-heading === sub-sub-heading == another = world ``` displays as...

> I fear that `image.bitmap(..colors)` would both be slow and not super useful if you want to generate the pixels via a WASM plugin. Something to provide RGBA `bytes` directly...