From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Parsing ConTeXt errors
Date: Thu, 13 Oct 2016 20:37:38 +0200 [thread overview]
Message-ID: <b2a76407-f6a2-8ad9-8e0b-9f19ca42f9e8@wxs.nl> (raw)
In-Reply-To: <ntkoqp$gag$1@blaine.gmane.org>
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).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-13 18: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
2016-10-11 22:13 ` Hans Hagen
2016-10-12 7:30 ` Nicola
2016-10-13 18:37 ` Hans Hagen [this message]
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=b2a76407-f6a2-8ad9-8e0b-9f19ca42f9e8@wxs.nl \
--to=pragma@wxs.nl \
--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).