On 2016-10-13 18:37:38 +, Hans Hagen said:
On 10/12/2016 9:30 AM, Nicola wrote:
On 2016-10-11 22:13:12 +, Hans Hagen said:
On 10/11/2016 9:37 PM, Nicola wrote:
On 2016-10-11 18:52:32 +, Alan Braslau said:
Of course, I *never* make MetaPost errors... ;-)
However, you can search
On 10/12/2016 9:30 AM, Nicola wrote:
On 2016-10-11 22:13:12 +, Hans Hagen said:
On 10/11/2016 9:37 PM, Nicola wrote:
On 2016-10-11 18:52:32 +, Alan Braslau said:
Of course, I *never* make MetaPost errors... ;-)
However, you can search the log file for
metapost> error:
Sure
On 2016-10-11 22:13:12 +, Hans Hagen said:
On 10/11/2016 9:37 PM, Nicola wrote:
On 2016-10-11 18:52:32 +, 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
On 10/11/2016 9:37 PM, Nicola wrote:
On 2016-10-11 18:52:32 +, 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:
because there are no
On 2016-10-11 18:52:32 +, 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/ma
Of course, I *never* make MetaPost errors... ;-)
However, you can search the log file for
metapost> error:
Alan
> On Oct 11, 2016, at 07:27, Nicola wrote:
>
> Hello,
>
> I'm trying to parse ConTeXt errors. TeX and Lua errors seem easy to parse
> (search for 'tex error' and 'lua err
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?