From: "Lukáš Procházka" <LPr@pontex.cz>
To: ConTeXt <ntg-context@ntg.nl>
Subject: Job done event
Date: Sun, 14 Feb 2016 08:46:56 +0100 [thread overview]
Message-ID: <op.yctbwip0f14xzu@lkzd-2013> (raw)
Hello,
during typesetting a document I'm collecting some information.
At the end (i.e. right before \stoptext or right after \stoptext), I'd need to perform an operation.
The way is to place some code before my code:
\starttext
...
\DoSomethingMine
\stoptext
But I'm looking for a way that the code inside document prepares the final operation and a way to avoid writing "\DoSomethingMine" before \stoptext (or \stopcomponent) - something being processed by ConTeXt naturally.
Something like:
\starttext
...
\startluacode
context.reactors.jobfinished = function(prev_op)
-- Do something mine
prev_op()
end
\stopluacode
...
\stoptext % ConTeXt to call "context.reactors.jobfinished" or similar implicitly
Does ConTeXt offer something like described? (Would be nice...)
Best regards,
Lukas
--
Ing. Lukáš Procházka | mailto:LPr@pontex.cz
Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz
Bezová 1658
147 14 Praha 4
Tel: +420 241 096 751
Fax: +420 244 461 038
___________________________________________________________________________________
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:[~2016-02-14 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 7:46 Lukáš Procházka [this message]
2016-02-14 14:38 ` Wolfgang Schuster
2016-02-15 14:08 ` Procházka Lukáš Ing.
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=op.yctbwip0f14xzu@lkzd-2013 \
--to=lpr@pontex.cz \
--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).