From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: What is the replacement for the 'stop_run' callback?
Date: Sun, 17 Oct 2010 18:24:08 +0200 [thread overview]
Message-ID: <4CBB2328.8040509@wxs.nl> (raw)
In-Reply-To: <AANLkTinNmZ3QqSqeNLosU88WJdLj3uoagEHO-oW+Y3e5@mail.gmail.com>
On 17-10-2010 4:06, Tad Ashlock wrote:
> I'm trying to update a ConTeXt module of mine. It does some data gathering
> during the ConTeXt run, and then processes it after the run is complete.
> This used to work last year:
>
> local id, err = callback.register('stop_run', new_stop_run_function)
>
> But now err is set to "callback 'stop_run' is frozen (actions performed at
> the end of a run)".
indeed
> After trying various approaches for a couple of hours, I'm calling for help.
> :)
> Here's what I ended up with:
>
> \startluacode
> print('%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% TEST1')
> local function after_run (head, groupcode)
> print('%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% TEST2')
> return head, true
> end
> nodes.tasks.appendaction('finalizers','after','after_run')
> \stopluacode
> \starttext
> \input knuth
> \stoptext
>
> In the output, I see the TEST1 line, but not the TEST2 line.
because after_run is not seen,
function myprivatenamespace.after_run ...
nodes.tasks.appendaction('finalizers','after','myprivatenamespace.after_run')
> I don't know what "head" and "groupcode" are, but those seem to be the
> expected parameters for an action. I don't know why it returns "head,
> true", but that was recommended in a posting (
> http://archive.contextgarden.net/message/20100410.005025.76ac9efd.en.html).
whatever, it's not the place to hook in your finalizer as there
finalizers are just a specific place in node list processing
> I have no idea if 'finalizers' is the right parameter, but I didn't see any
> others that looked like it could be synonymous with 'stop_run'.
You can use (preferable no messages there):
luatex.registerstopactions(yourfunction)
or for messages:
statistics.register("banner",function() return "text" end)
in this case returning false (or nil) will not show the statistic which
makes sense if there's nothing useful to report.
At some point there will be a formal description for this.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-10-17 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 14:06 Tad Ashlock
2010-10-17 16:24 ` Hans Hagen [this message]
2010-10-19 12:52 ` Tad Ashlock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CBB2328.8040509@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).