ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <gesang@stud.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mkiv: way to signal extra run(s)
Date: Sat, 29 Sep 2012 16:24:00 +0200	[thread overview]
Message-ID: <20120929142400.GA19172@tartaros> (raw)
In-Reply-To: <5066F8E2.9010701@gmx.net>


[-- Attachment #1.1: Type: text/plain, Size: 1572 bytes --]

···<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”.)

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
> ___________________________________________________________________________________

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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
___________________________________________________________________________________

  reply	other threads:[~2012-09-29 14:24 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 [this message]
2012-09-29 15:08   ` Peter Rolf
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=20120929142400.GA19172@tartaros \
    --to=gesang@stud.uni-heidelberg.de \
    --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).