From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Line number in "tex error"
Date: Fri, 25 Apr 2014 10:00:35 +0200 [thread overview]
Message-ID: <535A1623.10201@wxs.nl> (raw)
In-Reply-To: <CAHy-LL_feq_xDvuuj1G4SJUnJfEMaM_Cic4jFcP7h_Umda=cpA@mail.gmail.com>
On 4/25/2014 6:44 AM, Mikael P. Sundqvist wrote:
> If I want to catch the errors from the log file, is the best way to
> grep for "tex error" or something else? In this case the line is not
> correct there, but correct when the lines of the file is printed...
it relates to an indirect error: commands are of always expanded when
you think they are, some are delayed; also, blank is handled partially
in lua which then prints back stuff to tex which in turn can have an
error in code you never see (so, line 8 is in some internal buffer with
generated code)
in due time i can probably make error messages better but given the
nature of the macro language it will never be 100% ok
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2014-04-25 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 20:05 Mikael P. Sundqvist
2014-04-24 20:55 ` Hans Hagen
2014-04-25 4:44 ` Mikael P. Sundqvist
2014-04-25 8:00 ` Hans Hagen [this message]
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=535A1623.10201@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).