Hans Hagen wrote:
It depends on your document. We have workflows where we can do with one pass in which case we run with --once (--runs=2 or so)
Future versions of context mkiv might need one run less (in some cases) or one perceived run (which saves startup cycles) but as Wolgangs explained already, in more complex cases we cannot do with less runs as any change haping now can influence something a few pages back which in turn might influence what follows.
Normally, when you correct only typos there will be no multiple runs.
MkIV already is more efficient as we now always assume an advanced pdf backend so that we don't need to use the MkII the object reference mechanism.
Hans
In my example I can't even get \pagenumber to work correctly. If I replace my \test macro with \pagenumber, the first 4 pages all print page "1" (since it's still the same paragraph). Is there anything I can do about that? (Of course my main concern is the original problem of not catching page breaks to reset a variable). I also can't quite work out a multi-pass solution ... the only way I could imagine how it could work is by storing the content I would like to print together with the coordinates it was printed to in the first run, and in the second run evaluate from these information when a page break occured and modify the data accordingly. But I'm a bit lost here where to start ... my TeX knowledge is rather basic and I don't know anything about the luatex internals so I don't know if there are any events I could hook (and when and where to hook them :-/). I would be very grateful if you could point me in a direction I can work forward from - I can only guess that there are similar mechanisms in the already existing MkIV code ... although the \pagenumber problem seems to indicate that it might be near to impossible :-/ Best Regards, Andreas.