From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/8918 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Two quickies Date: Sun, 04 Aug 2002 23:38:43 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <5.1.0.14.1.20020804233050.02dd66d8@remote-1> References: <5.1.0.14.1.20020803174234.03998c78@remote-1> <5.1.0.14.1.20020803174234.03998c78@remote-1> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Trace: main.gmane.org 1035399282 31446 80.91.224.250 (23 Oct 2002 18:54:42 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:54:42 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: Glenn R Williams In-Reply-To: <1028401297.2175.29.camel@adipogo.adi.com> Xref: main.gmane.org gmane.comp.tex.context:8918 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:8918 At 03:01 PM 8/3/2002 -0400, Glenn R Williams wrote: >Hi All, > >Two quick questions: > >1. Is there a variable I can set to have all the temporary work files > placed in a separate directory for texexec runs? no, although this is on the to do list btw it is possible to run files that come from an other path, so you can co to a temp path, run texexec with --path=sourcepath, and copy the result back >2. I have a project/product/component structure, and all works fine > except that in my environment I have an abbreviation file which > I \input in the environment file. when I try to generate a document > from one of the product subdirectories, tex can't find the input > file. The envirnment file and the abbreviation file are are in the > same directory. A bit like this: > > /main_directory > tri_env.tex (the environment file) > tri_abbrev (the abbreviation file) > tri_proj (the project file) > /product1 > tri_prod.tex (the product file) > >I am executing texec from the "product1" directory. There are several ways to control paths; using \input is a bit dangerous since it looks in the current path and in the main tex tree which can lead to funny results (loading the wrong files) There a few ways out: (1) an ugly one: \input ../tri_abbrev (2) since env are taken from . ../ ../../ you can use: \environment tri_abbrev given that the file looks like \startenvironment ... \stopenvironment (3) you can also explicitly set the paths to look at (env and components and alike) using \usepath[...,...,...] or even the recently added: \usesubpath[...,...,...] This is typically the control needed for more complex workflows (4) as a last resort there are commands in supp-fil.tex, like \readfile \readlocfile \readsysfile Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------