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

On 2016-10-11 22:13:12 +0000, Hans Hagen said:

On 10/11/2016 9:37 PM, Nicola wrote:

...

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:

because there are no lines ... the library gets strings

Would it be possible to report at least the location of the enclosing \...MP... block? Nicola

On 2016-10-13 18:37:38 +0000, Hans Hagen said:

On 10/12/2016 9:30 AM, Nicola wrote:

...

On 2016-10-11 22:13:12 +0000, Hans Hagen said:

...

On 10/11/2016 9:37 PM, Nicola wrote:

...

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:

because there are no lines ... the library gets strings

Would it be possible to report at least the location of the enclosing \...MP... block?

it will always be the line where such a block ends, i adapted the message a bit

tex error > mp error on line 51 in file e:/tmp/oeps.tex:

...

...

foo ! Isolated expression. <to be read again> ; <*> ...draw fullcircle scaled (i) ; endfor ; foo ;

I couldn't find an `=' or `:=' after the expression that is shown above this error message, so I guess I'll just ignore it and carry on.

(the extra details at the end will be available in the next luatex binary as it needs an updated mplibrary).

Looks good, looking forward to trying it! Nicola