From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Error Line Number
Date: Sat, 14 Jan 2012 09:29:38 +0100 [thread overview]
Message-ID: <CAG5iGsDjuGcWG-BePMuJQ9xqiXmvSLrDi7MPkVZ2YQsb9-2pHQ@mail.gmail.com> (raw)
In-Reply-To: <1326498906.8032.2.camel@kip-laptop>
[-- Attachment #1.1: Type: text/plain, Size: 1034 bytes --]
On Sat, Jan 14, 2012 at 12:55 AM, Kip Warner <kip@thevertigo.com> wrote:
> On Fri, 2012-01-13 at 10:08 +0100, luigi scarso wrote:
> > Usually the strategy is to isolate the culprit by including progressively
> > lengthy chunks of tex
> > from the begin to end
> > and then narrowing the selection until you find a macro or paragraph.
> > Then surround it with
> > \tracingall
> > ...
> > \trancingnone
> > and you have a *huge* amount of informations.
> >
> > (btw, discover where an error happens it's known to be problematic due
> > the inherently asynchronous nature of TeX
> > and the macro programming language, where expansion can be very hard
> to
> > understand)
>
> That sounds very tedious and is definitely a major problem with ConTeXt.
> But like you said, it's difficult to alleviate based on how all of its
> components were designed.
>
> It's not a problem of ConTeXt, it's a problem of TeX , at least when you
use a complex macro format
like LaTeX or ConTeXt. It's the nature of the macro language.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1497 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2012-01-14 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 0:15 Kip Warner
2012-01-12 10:13 ` Hans Hagen
2012-01-12 19:11 ` Kip Warner
2012-01-13 9:08 ` luigi scarso
2012-01-13 13:36 ` Hans Hagen
2012-01-13 23:55 ` Kip Warner
2012-01-14 8:29 ` luigi scarso [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=CAG5iGsDjuGcWG-BePMuJQ9xqiXmvSLrDi7MPkVZ2YQsb9-2pHQ@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--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).