texexec.ini not read
I was trying to make the stand along context work with cygwin using cygwin ruby. Following the advice on the wiki of adding /scripts/context/ruby to rubylib, everything works fine. However, I am not able to enable write18. I copied texexec.rme to texexec.ini and added -shell-escape to all set TeXPassString in texexec.ini. However, I still get system(mpost .....) disabled in my log file. Reading through newtexexec.rb it seems that it does not check the ini file. Is this correct? Or am I missing something. Aditya -- Aditya Mahajan, EECS Systems, University of Michigan http://www.eecs.umich.edu/~adityam || Ph: 7342624008
<--- On Feb 28, Aditya Mahajan wrote --->
I was trying to make the stand along context work with cygwin using cygwin ruby. Following the advice on the wiki of adding /scripts/context/ruby to rubylib, everything works fine. However, I am not able to enable write18. I copied texexec.rme to texexec.ini and added -shell-escape to all set TeXPassString in texexec.ini. However, I still get
system(mpost .....) disabled
in my log file. Reading through newtexexec.rb it seems that it does not check the ini file. Is this correct? Or am I missing something.
Strange. If I run the command for dos command prompt, I get system (mpost .....) executed It seems that texexec is looking at different profiles under cygwin. Or rather, for some reason texexec can not find the correct file in cygwin. I am attaching both log files. There is not much difference there. It seems that I still need to work with cmd rather than bash :-( Any hints will be appreciated. Aditya -- Aditya Mahajan, EECS Systems, University of Michigan http://www.eecs.umich.edu/~adityam || Ph: 7342624008
Oops, forgot to attach the logs <--- On Mar 1, Aditya Mahajan wrote --->
<--- On Feb 28, Aditya Mahajan wrote --->
I was trying to make the stand along context work with cygwin using cygwin ruby. Following the advice on the wiki of adding /scripts/context/ruby to rubylib, everything works fine. However, I am not able to enable write18. I copied texexec.rme to texexec.ini and added -shell-escape to all set TeXPassString in texexec.ini. However, I still get
system(mpost .....) disabled
in my log file. Reading through newtexexec.rb it seems that it does not check the ini file. Is this correct? Or am I missing something.
Strange. If I run the command for dos command prompt, I get system (mpost .....) executed
It seems that texexec is looking at different profiles under cygwin. Or rather, for some reason texexec can not find the correct file in cygwin. I am attaching both log files. There is not much difference there.
It seems that I still need to work with cmd rather than bash :-( Any hints will be appreciated.
Aditya
-- Aditya Mahajan, EECS Systems, University of Michigan http://www.eecs.umich.edu/~adityam || Ph: 7342624008
Aditya Mahajan wrote:
Oops, forgot to attach the logs
<--- On Mar 1, Aditya Mahajan wrote --->
<--- On Feb 28, Aditya Mahajan wrote --->
I was trying to make the stand along context work with cygwin using cygwin ruby. Following the advice on the wiki of adding /scripts/context/ruby to rubylib, everything works fine. However, I am not able to enable write18. I copied texexec.rme to texexec.ini and added -shell-escape to all set TeXPassString in texexec.ini. However, I still get
system(mpost .....) disabled
in my log file. Reading through newtexexec.rb it seems that it does not check the ini file. Is this correct? Or am I missing something.
Strange. If I run the command for dos command prompt, I get system (mpost .....) executed
It seems that texexec is looking at different profiles under cygwin. Or rather, for some reason texexec can not find the correct file in cygwin. I am attaching both log files. There is not much difference there.
It seems that I still need to work with cmd rather than bash :-( Any hints will be appreciated.
did you enable write 18 in texmf.cnf?
Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
<--- On Mar 1, Hans Hagen wrote --->
Aditya Mahajan wrote:
Oops, forgot to attach the logs
<--- On Mar 1, Aditya Mahajan wrote --->
<--- On Feb 28, Aditya Mahajan wrote --->
I was trying to make the stand along context work with cygwin using cygwin ruby. Following the advice on the wiki of adding /scripts/context/ruby to rubylib, everything works fine. However, I am not able to enable write18. I copied texexec.rme to texexec.ini and added -shell-escape to all set TeXPassString in texexec.ini. However, I still get
system(mpost .....) disabled
in my log file. Reading through newtexexec.rb it seems that it does not check the ini file. Is this correct? Or am I missing something.
Strange. If I run the command for dos command prompt, I get system (mpost .....) executed
It seems that texexec is looking at different profiles under cygwin. Or rather, for some reason texexec can not find the correct file in cygwin. I am attaching both log files. There is not much difference there.
It seems that I still need to work with cmd rather than bash :-( Any hints will be appreciated.
did you enable write 18 in texmf.cnf?
Thanks for the hint. I had enabled it in texmf-local/web2c/texmf.cnf (in fact it was already set to t). Now, I went and edited texmf/web2c/texmf.cnf and set shell escape there to be true, and everything works fine. But this is strange. I thought that texmf-local will get preference over main texmf. Perhaps I did something terribly wrong in creating a setuptex for cygwin bash. I guess it is a problem with a clash of windows and unix file naming conventions. Can anyone shed some light on what is going on. This is not too important as everything is working properly (I hope). This is my setuptex for bash. For dos, I use the setuptex.bat that comes with context. #!/usr/bin/bash export TEXROOT=E:/isoimage/usr/local/context/tex # export TEXROOT=/e/isoimage/usr/local/context/tex export UNIXTEXROOT=/e/isoimage/usr/local/context/tex export TEXMFMAIN=$TEXROOT/texmf export TEXMFLOCAL=$TEXROOT/texmf-local export TEXMFFONTS=$TEXROOT/texmf-fonts export TEXMFEXTRA=$TEXROOT/texmf-extra export TEXMFPROJECT=$TEXROOT/texmf-aditya export TEXMFOS=$TEXROOT/texmf-mswin export PATH=$UNIXTEXROOT/texmf-mswin/bin:$PATH export VARTEXMF=$TMP/texmf-var export TEXMFCNF=$TEXROOT/texmf{-local,}/web2c export TEXMF='{$TEXMFOS,$TEXMFPROJECT,$TEXMFFONTS,$TEXMFLOCAL,$TEXMFEXTRA,!!$TEXMFMAIN}' export TEXMFDBS=$TEXMF export TEXFORMATS='$TEXMFOS/web2c/{$engine,}' export MPMEMS=$TEXFORMATS export TEXPOOL=$TEXFORMATS export MPPOOL=$TEXPOOL -- Aditya Mahajan, EECS Systems, University of Michigan http://www.eecs.umich.edu/~adityam || Ph: 7342624008
Aditya Mahajan wrote:
I was trying to make the stand along context work with cygwin using cygwin ruby. Following the advice on the wiki of adding /scripts/context/ruby to rubylib, everything works fine. However, I am not able to enable write18. I copied texexec.rme to texexec.ini and added -shell-escape to all set TeXPassString in texexec.ini. However, I still get
system(mpost .....) disabled
in my log file. Reading through newtexexec.rb it seems that it does not check the ini file. Is this correct? Or am I missing something.
if you run the ruby version of texexec, texexec.ini is not used, since there is no longer an ini file needed Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (2)
-
Aditya Mahajan -
Hans Hagen