From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mkiv: way to signal extra run(s)
Date: Sat, 29 Sep 2012 17:08:11 +0200 [thread overview]
Message-ID: <50670EDB.70206@gmx.net> (raw)
In-Reply-To: <20120929142400.GA19172@tartaros>
Am 29.09.2012 16:24, schrieb Philipp Gesang:
> ···<date: 2012-09-29, Saturday>···<from: Peter Rolf>···
>
>> Hi,
>>
>> just wondering. Is there a official way to signal ConTeXt from a module,
>> that an extra run is needed?
>
> Hi Peter, some time ago I got this answer from Hans:
> http://www.mail-archive.com/ntg-context@ntg.nl/msg45820.html
> (Today the table is “job.variables.tobesaved”.)
>
Hi Philipp,
that should work. I was planing to save the graphic hash data (id-> file
name) as lua file anyway and make use of that data in the following runs
(compare new and old hash). Storing a checksum of that file should be
all I need then.
Thanks for your help :-)
Peter
> Hth
> Philipp
>
>>
>> I started thinking about adding bookkeeping for the created run time
>> graphics. Graphic related changes can then be detected and, if
>> necessary, extra runs can be started to update the changed graphics.
>>
>> I need the second run to create and start the ImageMagick batch script,
>> but the collected info in the *.tuc file prevents ConTeXt from starting
>> a second/third run. Currently I use a batch file that simply deletes the
>> *.tuc file and then calls 'context'. As there is no bookkeeping, all the
>> graphics are recreated then.
>>
>>
>> Peter
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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:[~2012-09-29 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 13:34 Peter Rolf
2012-09-29 14:24 ` Philipp Gesang
2012-09-29 15:08 ` Peter Rolf [this message]
2012-09-29 21:59 ` Aditya Mahajan
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=50670EDB.70206@gmx.net \
--to=indiego@gmx.net \
--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).