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