--silent and so on
Hi everybody I am a current context user since now many years and in particular I use it on linux with automatic compilation with a bash script detecting any modifications of the .tex file. In order for this to work I used with previous versions the "--nonstopmode --batchmode --silent --noconsole" compilation options. With these options with a new error in the .tex files with old versions of mkiv the previous pdf produced was not changed. Now with lmtx, appears a single page pdf file with ERROR written on it. Are there compulations options with lmtx in order to have something similar as before ? Any ideas ? Thanks
thierry horsin schrieb am 22.07.2020 um 17:57:
Hi everybody
I am a current context user since now many years and in particular I use it on linux with automatic compilation with a bash script detecting any modifications of the .tex file. In order for this to work I used with previous versions
the "--nonstopmode --batchmode --silent --noconsole" compilation options.
With these options with a new error in the .tex files with old versions of mkiv the previous pdf produced was not changed. Now with lmtx, appears a single page pdf file with ERROR written on it. Are there compulations options with lmtx in order to have something similar as before ?
context --nodummy <file> Wolfgang
Thanls a lot. Thierry Le 22/07/2020 à 18:08, Wolfgang Schuster a écrit :
thierry horsin schrieb am 22.07.2020 um 17:57:
Hi everybody
I am a current context user since now many years and in particular I use it on linux with automatic compilation with a bash script detecting any modifications of the .tex file. In order for this to work I used with previous versions
the "--nonstopmode --batchmode --silent --noconsole" compilation options.
With these options with a new error in the .tex files with old versions of mkiv the previous pdf produced was not changed. Now with lmtx, appears a single page pdf file with ERROR written on it. Are there compulations options with lmtx in order to have something similar as before ?
context --nodummy <file>
Wolfgang ___________________________________________________________________________________
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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
On 22 Jul 2020, at 17:57, thierry horsin
wrote: Hi everybody
I am a current context user since now many years and in particular I use it on linux with automatic compilation with a bash script detecting any modifications of the .tex file. In order for this to work I used with previous versions
the "--nonstopmode --batchmode --silent --noconsole" compilation options.
Somewhat related question: is there a way to get rid of the “This is LuaMetaTeX, Version 2.06.18 “ line on the terminal ? Best wishesm Taco
On 7/23/2020 2:39 PM, Taco Hoekwater wrote:
On 22 Jul 2020, at 17:57, thierry horsin
wrote: Hi everybody
I am a current context user since now many years and in particular I use it on linux with automatic compilation with a bash script detecting any modifications of the .tex file. In order for this to work I used with previous versions
the "--nonstopmode --batchmode --silent --noconsole" compilation options.
Somewhat related question: is there a way to get rid of the
“This is LuaMetaTeX, Version 2.06.18 “
line on the terminal ?
Ah, you want to completely hide that tex is used, just in case someone who watches a run gets bad feelings (and expectations) due to earlier experiences, like ever being forced to use the backslasg driven language during education ... "Oh no, please, not TeX again!". Read: you need a hook where you can change it to "typeset on my ipad" or so, like: \starttext \ctxlua { texio.write_nl( "Typeset on my " .. string.char(27) .. "[32;5;7m" .. "IPAD" .. string.char(27) .. "[0m" .. " by me!" ) } \stoptext Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
On 23 Jul 2020, at 16:21, Hans Hagen
wrote: On 7/23/2020 2:39 PM, Taco Hoekwater wrote:
On 22 Jul 2020, at 17:57, thierry horsin
wrote: Hi everybody
I am a current context user since now many years and in particular I use it on linux with automatic compilation with a bash script detecting any modifications of the .tex file. In order for this to work I used with previous versions
the "--nonstopmode --batchmode --silent --noconsole" compilation options. Somewhat related question: is there a way to get rid of the “This is LuaMetaTeX, Version 2.06.18 “ line on the terminal ? Ah, you want to completely hide that tex is used, just in case someone who watches a run gets bad feelings (and expectations) due to earlier experiences, like ever being forced to use the backslasg driven language during education ... "Oh no, please, not TeX again!”.
Actually, I am trying to capture my (lua-generated) console output to a processing pipe that expects a html page. Best, Taco
participants (4)
-
Hans Hagen
-
Taco Hoekwater
-
thierry horsin
-
Wolfgang Schuster