On 7 Apr 2008 at 20:22, ntg-context-request@ntg.nl wrote:
I tried to make my first luatex-steps with the following wiki-example ------------------------------------- \usetypescript[palatino] \setupbodyfont[palatino,12pt] effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek
\sc effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek ------------------------------------- after adding a \start/stoptext pair I get in 4 runs the following error:
Exactly how did you run luatex? The canonical way is
texexec --luatex tst3
but I expect you are using some editor interface?
I am using scite with the following command: texmfstart texexec --autopdf --luatex tst3.tex If I try: 'texexec --luatex tst3' I get two runs with -------------------------------------------- {d:/context/tex/texmf/fonts/map/dvips/tex-gyre/qpl-ec.map} fonts : using map file: original-youngryu-px {d:/context/tex/texmf-context/fonts/map/pdftex/context/original- youngryu-px.map} [1.1] systems : end file tst3 at line 8 ){d:/context/tex/texmf/fonts/enc/dvips/tex-gyre/q-ec-sc.enc}fclose: No such file or directory fclose: No such file or directory ! Emergency stop. <*> tst3.tex ! ==> Fatal error occurred, no output PDF file produced! LuaTools | running command: luatex --fmt="d:/context/tex/texmf- cache/luatex- cache/context/c80dc1fd5292ec817c6e82c295beaf1e/formats/cont-en" -- lua="d:/context/tex/texmf-cache/luatex- cache/context/c80dc1fd5292ec817c6e82c295beaf1e/formats/cont-en.luc" "tst3.tex" "" LuaTools | LuaTools | runtime: 23.213 secondsTeXUtil | parsing file tst3.tui -------------------------------------------- Wolfgang
Hi, Wolfgang Werners-Lucchini wrote:
I am using scite with the following command: texmfstart texexec --autopdf --luatex tst3.tex
I simply have no idea. I do not understand why windows would object to closing a file that doesn't exist (not even how it could be possible for an opened file to not exist). It could be a simple matter of a missing file that somehow luatex fails to check for during opening so it is not discovered until it attempts to close the file, but even if that is true, I have no idea how to debug anything on windows. It could also be a (more complicated) problem triggered by disk synchronisation issues in Windows itself. We have been bitten by those before (what is your windows flavour?) In either case, someone else has to come up with tests and/or fix attempts. The only advice I can give is to reinstall context using the new minimals and see if that helps any. http://wiki.contextgarden.net/ConTeXt_Minimals Sorry, Taco
participants (2)
-
Taco Hoekwater
-
Wolfgang Werners-Lucchini