From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/55609 Path: news.gmane.org!not-for-mail From: Andreas Schneider Newsgroups: gmane.comp.tex.context Subject: Re: \everyaftershipout isn't "called" for every pagebreak Date: Sun, 17 Jan 2010 22:16:41 +0100 Message-ID: References: <36ACBB12-6EB5-4ED9-A7A0-70F1CDDEE50D@googlemail.com> <4B53761C.3070106@wxs.nl> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1263763090 3028 80.91.229.12 (17 Jan 2010 21:18:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 17 Jan 2010 21:18:10 +0000 (UTC) To: ntg-context@ntg.nl Original-X-From: ntg-context-bounces@ntg.nl Sun Jan 17 22:18:01 2010 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by lo.gmane.org with esmtp (Exim 4.50) id 1NWcVN-00033N-MA for gctc-ntg-context-518@m.gmane.org; Sun, 17 Jan 2010 22:17:53 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 91A45C9B99; Sun, 17 Jan 2010 22:17:45 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id JrBBxXXV5fl6; Sun, 17 Jan 2010 22:17:26 +0100 (CET) Original-Received: from balder.ntg.nl (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 59900C9D0D; Sun, 17 Jan 2010 22:17:26 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 70B2FC9D0D for ; Sun, 17 Jan 2010 22:17:21 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kRYxWwcT5wO9 for ; Sun, 17 Jan 2010 22:17:09 +0100 (CET) Original-Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by balder.ntg.nl (Postfix) with ESMTP id DDD21C9B99 for ; Sun, 17 Jan 2010 22:17:08 +0100 (CET) Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NWcUa-0002lu-QW for ntg-context@ntg.nl; Sun, 17 Jan 2010 22:17:04 +0100 Original-Received: from p54b4d1d0.dip.t-dialin.net ([84.180.209.208]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Jan 2010 22:17:04 +0100 Original-Received: from aksdb by p54b4d1d0.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Jan 2010 22:17:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Followup-To: gmane.comp.tex.context Original-Lines: 40 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p54b4d1d0.dip.t-dialin.net User-Agent: KNode/4.3.4 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:55609 Archived-At: 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. ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________