From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: markiv, "output written on..."
Date: Tue, 16 Dec 2008 19:32:05 +0100 [thread overview]
Message-ID: <4947F425.2040704@wxs.nl> (raw)
In-Reply-To: <m2iqpkyq25.fsf@levana.de>
Patrick Gundlach wrote:
> Hi Hans,
>
>>> when I run a markiv file I don't get any message of the resulting pdf
>>> file. Is this done on purpose?
>> probably (i overload some things)
>
> May I then ask for a change in behaviour? I'd like to parse the messages
> and search for the final pdf.
keep in mind that context --result might overload the name so we cannot
use jobname here.
to cont-new.mkiv add:
\ctxlua{
ctx.register_statistics("result saved in file", "\letterpercent
s.\letterpercent s", function()
return "\outputfilename", (tex.pdfoutput>0 and "pdf") or "dvi"
end)
}
then you can parse for
mkiv lua stats : result saved in file - x.pdf
(i'll add this)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2008-12-16 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 20:08 Patrick Gundlach
2008-12-16 3:54 ` Yue Wang
2008-12-16 8:49 ` Hans Hagen
2008-12-16 10:25 ` Hans Hagen
2008-12-16 17:42 ` Patrick Gundlach
2008-12-16 18:32 ` Hans Hagen [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=4947F425.2040704@wxs.nl \
--to=pragma@wxs.nl \
--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).