I try to process a ConTeXt project residing in a directory different from the
current directory (where context is called), imagine e.g. a NFS mounted
directory on a different host.
I tried to point context to the project directory
by specifying it by the command line option
--path=absolute_path_to
On 2012-04-15 Helge Blischke wrote:
> I try to process a ConTeXt project residing in a directory different from
> the current directory (where context is called), imagine e.g. a NFS mounted
> directory on a different host.
NFS is transparent to the applications and should work the same way
as lo
On 15-4-2012 23:57, Helge Blischke wrote:
I try to process a ConTeXt project residing in a directory different from the
current directory (where context is called), imagine e.g. a NFS mounted
directory on a different host.
I tried to point context to the project directory
by specifying it by the
Hans Hagen wxs.nl> writes:
>
> On 15-4-2012 23:57, Helge Blischke wrote:
> > I try to process a ConTeXt project residing in a directory different from
> > the
> > current directory (where context is called), imagine e.g. a NFS mounted
> > directory on a different host.
> >
> > I tried to point
On 16-4-2012 15:00, Helge Blischke wrote:
Hans Hagen wxs.nl> writes:
On 15-4-2012 23:57, Helge Blischke wrote:
I try to process a ConTeXt project residing in a directory different from the
current directory (where context is called), imagine e.g. a NFS mounted
directory on a different host.
On Mon, 16 Apr 2012, Hans Hagen wrote:
On 16-4-2012 15:00, Helge Blischke wrote:
Hans Hagen wxs.nl> writes:
On 15-4-2012 23:57, Helge Blischke wrote:
I try to process a ConTeXt project residing in a directory different from
the
current directory (where context is called), imagine e.g. a
On 16-4-2012 19:28, Aditya Mahajan wrote:
But this overwrites the default value of TEXMFHOME. If the mtxrun
--generate step were not needed, one could do the same with TEXMFPROJECT
tree.
One can indeed use texmfhome which is checked at runtime (but a large
one will take time of course esp on
Hans Hagen wxs.nl> writes:
>
> On 16-4-2012 19:28, Aditya Mahajan wrote:
>
> > But this overwrites the default value of TEXMFHOME. If the mtxrun
> > --generate step were not needed, one could do the same with TEXMFPROJECT
> > tree.
>
> One can indeed use texmfhome which is checked at runtime (
On Mon, 16 Apr 2012, Helge Blischke wrote:
By trial and eror I found out that
context --path=...
tries to run the scripts and programs within that directory
which leads to abort if e.g. the calling user has no write permission
there.
Can you summarize your results on the wiki?
On the other h
