Error Line Number
Hey folks, I get the following error message when attempting to compile my book, but it doesn't appear to say what file / line number is responsible. Is there a way to turn on file / line error messages, akin to what one sees with gcc? $ context Source/Handbook.tex --result="Handbook.pdf" --purgeresult resolvers | resolving | loading configuration file 'selfautodir:/share/texmf/web2c/contextcnf.lua' resolvers | resolving | loading configuration file '/usr/share/texmf/web2c/contextcnf.lua' mtx-context | run 1: luatex --fmt="/home/kip/.texmf-var/luatex-cache/context/e570cb3e0e3ab0118ca08dd148bbec7d/formats/cont-en" --lua="/home/kip/.texmf-var/luatex-cache/context/e570cb3e0e3ab0118ca08dd148bbec7d/formats/cont-en.lui" --backend="pdf" "Source/Handbook.tex" \stoptext This is LuaTeX, Version beta-0.71.0-2011122302 (rev 4358) \write18 enabled. resolvers > resolving > loading configuration file '/usr/share/texmf/web2c/contextcnf.lua' (Source/Handbook.tex ConTeXt ver: 2011.12.31 18:06 MKIV fmt: 2012.1.11 int: english/english system > cont-new.mkiv loaded (/usr/share/texmf/tex/context/base/cont-new.mkiv system > beware: some patches loaded from cont-new.mkiv ) system > Handbook.top loaded (Handbook.top) fonts > latin modern fonts are not preloaded languages > language en is active {/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map} fonts > preloading latin modern fonts (second stage) (/usr/share/texmf/tex/context/base/type-siz.mkiv) (/usr/share/texmf/tex/context/base/type-otf.mkiv) files > readfile > asked name: 'loc', not found {/usr/share/texmf/fonts/map/dvips/lm/lm-math.map}{/usr/share/texmf/fonts/map/dvips/lm/lm-rm.map} fonts > defining > forced type afm of stmary10 not found fonts > defining > font with asked name 'stmary10' is not found using lookup 'file' fonts > virtual math > loading font LMMath7-Regular subfont 9 with name stmary10.afm at 458752 is skipped, not found fonts > defining > forced type afm of stmary10 not found fonts > defining > font with asked name 'stmary10' is not found using lookup 'file' fonts > virtual math > loading font LMMath9-Regular subfont 9 with name stmary10.afm at 589824 is skipped, not found fonts > defining > forced type afm of stmary10 not found fonts > defining > font with asked name 'stmary10' is not found using lookup 'file' fonts > virtual math > loading font LMMath12-Regular subfont 9 with name stmary10.afm at 786432 is skipped, not found fonts > fallback modern rm 12pt is loaded (Source/Environment.tex resolvers > modules > loaded: 'units' (/usr/share/texmf/tex/context/base/m-units.mkiv< + /usr/share/texmf/tex/context/base/x-mathml.lua>) resolvers > modules > loaded: 'simplefonts' (/usr/share/texmf/tex/context/third/simplefonts/t-simplefonts.tex loading > ConTeXt User Module / Simplefonts <+ /usr/share/texmf/tex/context/third/simplefonts/t-simplefonts.lua>) fonts > beware: fontclass ignored (if needed use: [fontclass][size][settings]) ) ! Missing } inserted. <inserted text> } <to be read again> \vfill l.23 \vfill ? -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com
On 12-1-2012 01:15, Kip Warner wrote:
Hey folks,
I get the following error message when attempting to compile my book, but it doesn't appear to say what file / line number is responsible. Is there a way to turn on file / line error messages, akin to what one sees with gcc?
such a message comes from stored macros so there is no such information 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 -----------------------------------------------------------------
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? -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com
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
On 13-1-2012 10:08, luigi scarso wrote:> \tracingall \loggingall is faster (only log)
.... \trancingnone and you have a *huge* amount of informations.
----------------------------------------------------------------- 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 -----------------------------------------------------------------
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
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
On Sat, Jan 14, 2012 at 12:55 AM, Kip Warner
participants (3)
-
Hans Hagen -
Kip Warner -
luigi scarso