ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Two quickies
Date: Sun, 04 Aug 2002 23:38:43 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20020804233050.02dd66d8@remote-1> (raw)
In-Reply-To: <1028401297.2175.29.camel@adipogo.adi.com>

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
-------------------------------------------------------------------------


      parent reply	other threads:[~2002-08-04 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-03 15:43 [Greg Restall <Greg.Restall@mq.edu.au>] Hans Hagen
2002-08-03 19:01 ` Two quickies Glenn R Williams
2002-08-03 20:27   ` Two quickies - clarification Glenn R Williams
2002-08-04 21:38   ` Hans Hagen [this message]

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=5.1.0.14.1.20020804233050.02dd66d8@remote-1 \
    --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).