From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Can is somehow inspect the intermediate results of an mtxrun?
Date: Mon, 16 Mar 2020 10:16:33 +0100 [thread overview]
Message-ID: <C22C8CCF-6392-4C62-9E97-B209FF4F421B@rna.nl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1025 bytes --]
I have an mtxrun on a .tex file that has problems I need to debug.
The .tex file handles well, but whenMETAPOST has a go, it crashes. But after the run, I cannot inspect what source was fed to METAPOST. Can I inspect that (outside of what the log tells me)?
In this case, I know METAPOST is fed:
picture pic; x:=80.000; y:=200.000; w:=133.000; h:=53.000;pic := ApplicationComponentLogo( w, h, typeString) shifted (x, -y); draw pic;
but the log says this is wrong:
metapost log > >> unknown picture pic
metapost log > >> ApplicationComponentLogo
metapost log > ! Equation cannot be performed (unknown picture=numeric).
metapost log > <to be read again>
metapost log > (
metapost log > <*> ... h:=53.000;pic := ApplicationComponentLogo(
metapost log > w, h, typeString) shifted...
SoI need to inspect what is fed to METAPOST to see why METAPOST thinks pic or ApplicationComponentLogo have not been defined.
G
[-- Attachment #1.2: Type: text/html, Size: 3882 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2020-03-16 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 9:16 Gerben Wierda [this message]
2020-03-16 9:32 ` Hans Hagen
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=C22C8CCF-6392-4C62-9E97-B209FF4F421B@rna.nl \
--to=gerben.wierda@rna.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).