From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Parsing ConTeXt errors
Date: Tue, 11 Oct 2016 21:37:45 +0200 [thread overview]
Message-ID: <ntjf27$kfl$1@blaine.gmane.org> (raw)
In-Reply-To: <84815259-2635-459A-B7FA-1A74D134CEBE@cea.fr>
On 2016-10-11 18:52:32 +0000, Alan Braslau said:
> Of course, I *never* make MetaPost errors... ;-)
>
> However, you can search the log file for
> metapost > error:
Sure. But there is no line number. Compare with a typical TeX error:
tex error > tex error on line 210 in file /path/to/main.tex: !
Undefined control sequence
l.210 \sdkjdkjhkdkkjk
In the same line you see:
1) the type of error (tex error);
2) the line number;
3) the file in which the error occurs;
4) the error message.
For MetaPost errors, only 1) and 4) are given with the error; 3) may be
inferred
(by tracking `open source`/`close source` lines). But I see no trace of 2).
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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-10-11 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 13:27 Nicola
2016-10-11 18:52 ` Alan Braslau
2016-10-11 19:37 ` Nicola [this message]
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='ntjf27$kfl$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).