From: Hans Hagen <pragma@wxs.nl>
Subject: Re: ConTeXt "live"
Date: Fri, 02 Dec 2005 16:17:53 +0100 [thread overview]
Message-ID: <439065A1.6020102@wxs.nl> (raw)
In-Reply-To: <e5d3f2650512020625y5fa870e4tdc2b11ac00f80836@mail.gmail.com>
VnPenguin wrote:
>On 12/2/05, Hans Hagen <pragma@wxs.nl> 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
next prev parent reply other threads:[~2005-12-02 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 22:19 VnPenguin
2005-12-02 14:05 ` Hans Hagen
2005-12-02 14:25 ` VnPenguin
2005-12-02 15:17 ` Hans Hagen [this message]
2005-12-02 14:21 ` Patrick Gundlach
2005-12-02 14:30 ` VnPenguin
2005-12-02 15:17 ` Patrick Gundlach
2005-12-02 18:32 ` VnPenguin
2005-12-02 21:30 ` Patrick Gundlach
2005-12-03 11:56 ` Taco Hoekwater
2005-12-03 23:10 ` Christopher Creutzig
2005-12-04 0:13 ` Patrick Gundlach
2005-12-02 15:32 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=439065A1.6020102@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).