From: Tad Ashlock <tad.ashlock@gmail.com>
To: ntg-context@ntg.nl
Subject: What is the replacement for the 'stop_run' callback?
Date: Sun, 17 Oct 2010 08:06:16 -0600 [thread overview]
Message-ID: <AANLkTinNmZ3QqSqeNLosU88WJdLj3uoagEHO-oW+Y3e5@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1582 bytes --]
Hi All,
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)".
I see from the mailing list archive that registering user callbacks was
disallowed in February of this year (2010). I also saw some advice for
installing other new user processing (like 'pre_linebreak_filter'), but no
general advice for adapting to the lack of callbacks. (
http://archive.contextgarden.net/message/20100219.130524.b3857a0a.en.html)
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.
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).
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'.
[-- Attachment #1.2: Type: text/html, Size: 2296 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2010-10-17 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 14:06 Tad Ashlock [this message]
2010-10-17 16:24 ` Hans Hagen
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=AANLkTinNmZ3QqSqeNLosU88WJdLj3uoagEHO-oW+Y3e5@mail.gmail.com \
--to=tad.ashlock@gmail.com \
--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).