On Mon, 24 Mar 2008, Hans van der Meer wrote:
I looked up what Aditya said can be found in the wiki and did:
texmfstart texexec --module kpse:mult-ini.tex
I get the following output on my console: 108 ~/Temp/tex: texmfstart texexec --module kpse:mult-ini.tex /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:641:in `initialize': Permission denied - /usr/local/texlive/texmf-context/tex/context/base/mult-ini.ted (Errno::EACCES) from /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:641:in `open' from /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:641:in `documentation' from /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:629:in `each' from /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:629:in `documentation' from /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:2778:in `send' from /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:2778
The permissions of the directory involved can be seen from: ls -l /usr/local/texlive/texmf-context/tex/context ==> drwxr-xr-x 767 sysop staff 26078 11 mrt 18:31 base
That is, texexec tries to write into a directory for which has no write access. I operate normally as myself and only for the installation of software assume the role of system operator (to hinder rogue programs and protect myself from stupid deletes, for example).
Do I understand correctly from this, that unless one has write access to the tex installation directories one cannot typeset the module source? If so, I urge Hans Hagen to change this and let texexec and friends write into tmp directories or in the users current directory.
Sometimes I want to run texexec on a file in the different directory. In that case, I find it useful that texexec is run on the directory in which the file lies (otherwise things like \input and \component will not work properly)
But I might be wrong and having something other amiss.
You can just copy the file to a local directory and create the documentation. Aditya