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: Long compile time
Date: Tue, 31 Aug 1999 09:38:17 +0200	[thread overview]
Message-ID: <37CB8669.88D02413@wxs.nl> (raw)
In-Reply-To: <3.0.5.32.19990830194846.00b429d0@mail.northcoast.com>

David Arnold wrote:

> I have now had several people make a project suggestion as a means of
> assembling the various pieces of a large task. Hans has described the
> procedure below. I would like to give this a try, but I have a few
> questions before restructuring my documents.
> 
> 1. Do you recommend that I pursue this technique? I think yes?
> 
> 2. Here's how I like to structure my project directories;
> 
> f:\book
> f:\book\chap1
> f:\book\chap2
> f:\book\chap3
> f:\book\chap4
> f:\book\chap5
> f:\book\chap6
> f:\book\chap7
> f:\book\chap8
> f:\book\chap9
> f:\book\chap10
> 
> The directory f:\book contains my master document, master.tex. Each of the
> directories f:\book\chapi contains a file called chapi.tex and all of the
> files needed to construct that file, *.eps, *.pdf, *.m (matlab files), *.mp
> (Metapost files), etc. Each directory has a SIGNIFICANT number of files.
> This is how I like to work, because chunking everything into one directory
> would quickly become unmanageable, at least for me.
> 
> Now, knowing these parameters, am I still a candidate to use this
> project--product approach?

It all depends on where your project / product files go. Concerning
figures, you can set up the directories used with 

  \setupexternalfigures[directory={commaseparatedlist}] 

like: 

  \setupexternalfigures[directory={mps,eps,pdf}] 

For tex and other files, you can set the directories with:  

  \usepath[commaseparatedlist]

like: 

  \usepath[book,anotherbook,yetanotherbook]

To prevent problems with clashing files (think of context picking up a
tuo file from another path because your tex does recursive search)
depending on the file searched, context restricts the search. Figure
files for instance are search on the current path or one of the global
paths as set up (unless one of these is enabled). Environments are
searched upto three levels down (up) the tree, which means that you can
put shared environemnts, abbreviation definitions, etc in a parent
path.  Context really does its best to limit the search time. 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------


  reply	other threads:[~1999-08-31  7:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-29  2:48 David Arnold
1999-08-29 10:40 ` Hans Hagen
1999-08-31  2:48   ` David Arnold
1999-08-31  7:38     ` Hans Hagen [this message]
1999-08-30  7:05 ` Gilbert van den Dobbelsteen

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=37CB8669.88D02413@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).