On Sun, 25 Jun 2006, Idris Samawi Hamid wrote: > On Sun, 25 Jun 2006 17:27:41 -0600, John R. Culleton > <[EMAIL PROTECTED]> wrote: > >> I downloaded the justtex.zip and the context-linux.zip files >> into a work directory /usr/local/cont and unzipped them. Then I >> cd to the tex directory under that work directory. I made the >> the setuptex file executable and executed it with no apparent >> effect. Then I changed the path to point to >> /usr/local/cont/tex/texmf-linux/bin and ran mktexlsr. It followed >> the new path. I ran texexec --make --alone and it seemed to be >> successful.
setuptex just sets some system variables (TEXMF, TEXMFMAIN, TEXMFLOCAL and so on) and modifies the PATH, so you will not get any immediate feedback on whether it ran correctly or not. Depending on your shell you may have to "source setuptex path-to-setuptex" or just "setuptex path-to-setuptex" As a quick check to see if everything went fine, do "echo $TEXMF" before and after sourcing setuptex. > Just a guess: since you used the --alone switch, is there a path to the > current directory from which you invoked > texexec --make --alone > > Without the --alone switch the fmt file should go into \texmf-linux\web2c > or \texmf-linux\web2c\pdfetex, depending on your texexec.ini setup. IIRC, the new (ruby) texexec does not read texexec.ini. One possibility is that $TEXMFLOCAL is not set (as you did not run setuptex) so texexec did not know where to place the format files. This also happens with Miktex and texexec creates a directory pdfetex in the current directory and dumps the format files there. You can try moving the fmt files to /usr/loca/cont/tex/texmf-local/web2c/pdfetex Aditya _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
