The --silent parameter seems to have no effect. I still get messages listing every typescript in use on every pass: e.g., (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-exa.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-syn.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-enc.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-siz.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-map.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-spe.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-akb.tex) (./type-charter.tex The above is repeated about four times. All this trivia slows down the compile process significantly. I am using texexec 5.4.3. I get warning messages telling me to use texmfstart instead but since that script is not functional on my machine I just use texexec. It seems to work OK except for the --silent script. On Linux I can always say: texexec book.tex >/dev/null but this obscures error messages as well. -- John Culleton Able Indexing and Typesetting Precision typesetting (tm) at reasonable cost. Satisfaction guaranteed. http://wexfordpress.com
John R. Culleton wrote:
The --silent parameter seems to have no effect. I still get messages listing every typescript in use on every pass: e.g., (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-exa.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-syn.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-enc.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-siz.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-map.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-spe.tex) (/hdb1/usr/local/texlive/2005/texmf-dist/tex/context/base/type-akb.tex) (./type-charter.tex
The above is repeated about four times.
--silent only surpresses macro-generated messages, not the ones from TeX itself. For quieter runs, you can try --batch (\batchmode), but that will hide (and abort on) any errors in the file.
All this trivia slows down the compile process significantly.
For a real speedup, set \preloadtypescripts to true in your cont-sys.tex. It will stop context from loading the files over and over, instead loading it only once and interpreting the file completely in that one go. That is much faster (at the expense of always having the whole contents of those files in memory)
I am using texexec 5.4.3. I get warning messages telling me to use texmfstart instead but since that script is not functional on my
What do you mean with 'not functional'? No ruby installed? Cheers, Taco
On Saturday 12 August 2006 13:52, Taco Hoekwater wrote:
I am using texexec 5.4.3. I get warning messages telling me to use texmfstart instead but since that script is not functional on my
What do you mean with 'not functional'? No ruby installed?
Cheers, Taco _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
It simply does nothing. If ruby were not installed I would get an error message of some sort. It just exits immediately In fact ruby --help gives me instructions for using ruby so it is installed. BTW The trick you gave me with cont-sys.tex eliminates the font messages after the first pass. Thanks! -- John Culleton Able Indexing and Typesetting Precision typesetting (tm) at reasonable cost. Satisfaction guaranteed. http://wexfordpress.com
participants (2)
-
John R. Culleton -
Taco Hoekwater