VnPenguin wrote:
On 12/2/05, Hans Hagen <[EMAIL PROTECTED]> wrote:
it has to do with the tex distribution being configured as too paranoid
which means no writing
can you try the --notparanoid switch?
Just added this option to texexec, but it does not help.
The problem is still there.
i remember sucn problems but forgot what the trick was; you can only
sort out such things when you have access to the machine; the problem is
in kpse sitting in between
as patrick says, the problem is that
- with immediate write 18 one can launch any program, the only way out
of this is when one can only run scripts within the tree, but i don't
see that happen (hard to get aggreement upon)
- a more clever paranoid mode, where expanded paths are taken into
account; for instance, if paranoid means that ../blabla or blabla.bla
are looked at, it may mean that the period results in blocking, while
actually the expanded path may still be within the tree
actually, in the minimal distribution, such thinsg are taken care of:
% resource paths, can be used in paranoid situations (can be env vars);
there you find:
TXRESOURCES=rubish
MPRESOURCES=$TXRESOURCES
MFRESOURCES=$MPRESOURCES
% some extra paths for development trees (can be env vars)
CTXDEVTXPATH=rubish
CTXDEVMPPATH=rubish
CTXDEVMFPATH=rubish
TEXINPUTS.context =
.;{$TXRESOURCES}//;{$CTXDEVTXPATH}//;$TEXMF/{pdftex,pdfetex,etex,xetex,omega,tex}/{context,plain,generic,}//
MPINPUTS =
.;{$MFRESOURCES}//;{$CTXDEVMPPATH}//;$TEXMF/metapost/{context,base,}//
MFINPUTS =
.;{$MPRESOURCES}//;{$CTXDEVMFPATH}//;$TEXMF/metafont/{context,base,}//;{$TEXMF/fonts,$VARTEXFONTS}/source//
so, one can set the TXRESOURCE path (using texexec) and out of a sudden
that path (which may lay outside the tree) is acceptable
Hans
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
