From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Long compile time
Date: Sun, 29 Aug 1999 12:40:23 +0200 [thread overview]
Message-ID: <37C90E17.E652CEBF@wxs.nl> (raw)
In-Reply-To: <3.0.5.32.19990828194805.00872b30@mail.northcoast.com>
David Arnold wrote:
> For me, the most frustrating thing about ConTeXt seems to be the long time
> it takes to compile. I've read the texexex.pdf file and there are some nice
> hints in there to reduce the compile time. I still have two questions.
That's the sacrifice for a parameter driven package.
> 1. Can I reduce to a minimum the compile time by entering a comment in the
> first line of my file, something akin to
>
> %output=pdf
>
> that I use frequently? If this can be done, what is an optimal comment line
> for limiting the compile time?
Sometimes texexec --fast runs a bit faster. To prevent multiple runs,
say
texexex --once .....
> 2. Suppose I have a master document with
>
> \input chap1
> \input chap2
> \input chap3
>
> etc. Suppose I am working in chap3.tex and I only want to compile chap3. Of
> course, I can comment out
>
> %\input chap1
> %\input chap2
>
> but then I lose the correct numbering of pages, chapters, etc. Is there a
> better procedure?
A rather old feature of context is project support (pre texexec time,
when we were making collections of educational materials):
(project file: course.tex)
\startproject course
\environment commonsetups
\product book
\product exercises
\product answers
\product examn
\stopproject
(environment file: commonsetups.tex)
\startenvironment commonsetups
all kind of (layout) setups
\stopenvironment
(product file: book.tex)
\startproduct book
\project course
\environment booksetups
\component chap-1
\component chap-2
\stopproduct
(component file: chap-1.tex)
\startcomponent chap-1
\project course
\product book
... chapter 1 ...
\stopcomponent
etc etc
Now you can say:
texexec book
texexec chap-1
texexec chap-2
etc
It is possible to set up context in such a way that the book refs etc
migrate to the individual chapters, but this only makes sense in special
cases.
Maybe this relieves the pain of speed.
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
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-08-29 10:40 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 [this message]
1999-08-31 2:48 ` David Arnold
1999-08-31 7:38 ` Hans Hagen
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=37C90E17.E652CEBF@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).