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. -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com
signature.asc
Description: This is a digitally signed message part
___________________________________________________________________________________ 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 ___________________________________________________________________________________
