Rubem Vasconcelos Pacelli

> It is indeed something that cannot be solved nicely by Polylux without Typst offering some "state freezing". Is there any prospective about it?

Is there an opened issue in Typst addressing this topic? If no, it should be opened.

Totally agreed. This is a missing feature. What would be the syntax? I've found a workaround solution for your case in https://github.com/denisidoro/navi/issues/899#issuecomment-2214205720

> I agree, returning commands to eval via stdout is not really a good solution. Great! > But I'm happy to fix this, if we find a good solution. I...

> we need to somehow exit this new shell and then `cd` to the new directory. So... Why not just `exit`ing? I got the idea of activating/deactivating environments while going...

Well, maybe the problem is, once we spawn a new shell as a subprocess of the parent shell, we cannot run the `exit` command from the parent shell as a...

I know that. The point of this issue is to propose making this name built-in so that we don't need to name all elements as `"{}"` or something. If you...

From the manual > Elements after the group are not affected by the changes inside the group. Well, maybe I misunderstood, but `group()` should also prevent changes from being applied...

In fact, I can retrieve `test` by using `resolve()` and them using the resolved coordinates ```typ draw.get-ctx(ctx => { let (ctx, a) = coordinate.resolve(ctx, test) draw.content(test, [#a], frame: "rect", stroke:...

I was expecting that ```typ #import "@preview/cetz:0.2.2": canvas, plot, draw, coordinate, vector #set page(width: auto, height: auto, margin: .5cm) #canvas({ draw.rect((0,0), (1,1), name: "rect") let test = (rel: (0deg, 2),...