Hi, When running the five lines long file \starttext Bla bla \blank[foo] Bla bla \stoptext through context I get the error below (the foo in the blank is there to get an error, see the attached log file for the full log file). My question is why is context first telling me that the error is on line 8 and not 3? (In this particular example this is not a problem, but I'd like to grep for errors in the log file when running through the editor). I see that the error is later said to be at line 3... /Mikael ====== STARTERROR ====== tex error > error on line 8 in file /home/mickep/tmp/err.tex: ! Missing number, treated as zero <to be read again> f <argument> f oo \addaskedblankskip ..._vspacing_temp #1\dimexpr #2 \relax l.8 } \ctxcommand #12-\directlua {commands.#1} \spac_vspacing_yes_indeed ...mand {vspacing("#1")} \fi l.3 \blank[foo] 1 \starttext 2 Bla bla 3 \blank[foo] 4 Bla bla 5 \stoptext 6 ? ====== STOPERROR ======
On 4/24/2014 10:05 PM, Mikael P. Sundqvist wrote:
Hi,
When running the five lines long file
\starttext Bla bla \blank[foo] Bla bla \stoptext
through context I get the error below (the foo in the blank is there to get an error, see the attached log file for the full log file).
My question is why is context first telling me that the error is on line 8 and not 3? (In this particular example this is not a problem, but I'd like to grep for errors in the log file when running through the editor). I see that the error is later said to be at line 3...
It depends a bit on what luatex version you're running .. there can be errors in the source, in some macro (defined elsewhere), in lua code ... and context tries as good as it can to print the right code .. in this case the error is triggered deep down (foo is an undefined blank option and so a dimen is expected). 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, Apr 24, 2014 at 10:55 PM, Hans Hagen
On 4/24/2014 10:05 PM, Mikael P. Sundqvist wrote:
Hi,
When running the five lines long file
\starttext Bla bla \blank[foo] Bla bla \stoptext
through context I get the error below (the foo in the blank is there to get an error, see the attached log file for the full log file).
My question is why is context first telling me that the error is on line 8 and not 3? (In this particular example this is not a problem, but I'd like to grep for errors in the log file when running through the editor). I see that the error is later said to be at line 3...
It depends a bit on what luatex version you're running .. there can be errors in the source, in some macro (defined elsewhere), in lua code ... and context tries as good as it can to print the right code .. in this case the error is triggered deep down (foo is an undefined blank option and so a dimen is expected).
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 ----------------------------------------------------------------- ___________________________________________________________________________________ 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 ___________________________________________________________________________________
I see. I'm running the ConTeXt standalone. luatex --version This is LuaTeX, Version beta-0.79.1 (TeX Live 2014/dev) (rev 4972) In this case I made the error on purpose inserting foo in the blank. If I want to catch the errors from the log file, is the best way to grep for "tex error" or something else? In this case the line is not correct there, but correct when the lines of the file is printed... /Mikael
On 4/25/2014 6:44 AM, Mikael P. Sundqvist wrote:
If I want to catch the errors from the log file, is the best way to grep for "tex error" or something else? In this case the line is not correct there, but correct when the lines of the file is printed...
it relates to an indirect error: commands are of always expanded when you think they are, some are delayed; also, blank is handled partially in lua which then prints back stuff to tex which in turn can have an error in code you never see (so, line 8 is in some internal buffer with generated code) in due time i can probably make error messages better but given the nature of the macro language it will never be 100% ok 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 -----------------------------------------------------------------
participants (2)
-
Hans Hagen -
Mikael P. Sundqvist