From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mode *last in mkiv
Date: Mon, 19 Jul 2010 22:38:03 +0200 [thread overview]
Message-ID: <AANLkTilKOtE8pIws7lLD1KfS9Uqr3xIuueDO9G6LUnmS@mail.gmail.com> (raw)
In-Reply-To: <4C44B0FA.6090701@googlemail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1032 bytes --]
On Mon, Jul 19, 2010 at 10:09 PM, Wolfgang Schuster <
schuster.wolfgang@googlemail.com> wrote:
>
> why don't you use then a ctx file which process first the document and then
> MyAnalyze...
>
> yes I know.
The point is: while the *first mode is clear and can be managed inside
context,
the concept of last run is problematic.
If one wants to be sure that "this tex code will be parsed only at the last
run"
then the tex code must be enclose inside a \startmode[LAST]\stopmode
and processed with
#>context mydoc.tex && context --mode=LAST mydoc.tex
(let's forget of errors for the moment)
But if the tex code modify mydoc then the first context mydoc
is superfluous.
So in the end the tex code must do nothing of relevant, and hence it can be
replaced by an external program MyAnalyze
which in general must have as input the input source mydoc.tex, the output
file mydoc.pdf and the log mydoc.log
and processed with
#>context --batch mydocument.tex ; MyAnalyze mydoc.tex mydoc.pdf mydoc.log
to take care of errors.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1565 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
___________________________________________________________________________________
prev parent reply other threads:[~2010-07-19 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 11:30 luigi scarso
2010-07-19 17:24 ` Wolfgang Schuster
2010-07-19 17:37 ` luigi scarso
2010-07-19 17:56 ` Wolfgang Schuster
2010-07-19 18:26 ` luigi scarso
2010-07-19 19:21 ` Wolfgang Schuster
2010-07-19 20:00 ` luigi scarso
2010-07-19 20:09 ` Wolfgang Schuster
2010-07-19 20:38 ` luigi scarso [this message]
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=AANLkTilKOtE8pIws7lLD1KfS9Uqr3xIuueDO9G6LUnmS@mail.gmail.com \
--to=luigi.scarso@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).