ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Parsing ConTeXt errors
Date: Tue, 11 Oct 2016 15:27:01 +0200	[thread overview]
Message-ID: <ntipb3$f7r$1@blaine.gmane.org> (raw)

Hello,

I'm trying to parse ConTeXt errors. TeX and Lua errors seem easy to parse
(search for 'tex error' and 'lua error', respectively), but I have a couple of
problems with MetaPost messages.

First, when there are MetaPost errors, context/mtxrun exits with a zero exit
code. Is that intentional?

Second, as far as I see, there is no way to locate the error in the source
from the log. I can only retrieve the file causing the error (by searching for
an 'open source' line - very useful, btw), but no line number.

Am I missing something? I think it would be very useful to have at least an
approximate indication of the position of a MetaPost error.

Nicola



___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2016-10-11 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 13:27 Nicola [this message]
2016-10-11 18:52 ` Alan Braslau
2016-10-11 19:37   ` Nicola
2016-10-11 22:13     ` Hans Hagen
2016-10-12  7:30       ` Nicola
2016-10-13 18:37         ` Hans Hagen
2016-10-13 19:00           ` Nicola

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='ntipb3$f7r$1@blaine.gmane.org' \
    --to=nvitacolonna@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).