[NTG-context] Parsing ConTeXt errors

Nicola nvitacolonna at gmail.com
Tue Oct 11 21:37:45 CEST 2016


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




More information about the ntg-context mailing list