On Thu, Jan 12, 2012 at 8:11 PM, Kip Warner
On Thu, 2012-01-12 at 11:13 +0100, Hans Hagen wrote:
such a message comes from stored macros so there is no such information
So when you have a book of hundreds of pages in length split up over dozens of tex files and ConTeXt emits an error, how do you know what file / line number to examine?
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) -- luigi