ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: skipping parts in compiling
Date: Wed, 22 Feb 2006 16:44:38 +0100	[thread overview]
Message-ID: <6faad9f00602220744j593bf165tb4eb91b7ca2e4e4b@mail.gmail.com> (raw)
In-Reply-To: <5840b78786d212d447df88f448df53ba@di.unito.it>

> > If you mean "can I recompile only page 3 and 4 out of my 100-page book
> > and get the whole document" that answer is no I think. But there are
> > other ways.
> >
>
> I suspected.

Well, you also have
texmfstart newtexexec.rb --pfdcombine | copy | select | trim

I don't know how exactly to use them (to hans: lines 351-359 in
newtexexec.rb, "def copyortrim" seem to be broken a bit - wrong number
of arguments), but I guess that you could combine parts of your
document together again this way (I wouldn't use this approach
however).

But what's wrong with using modular approach (to compile just the
chapter or section you're currently working on, so that it compiles
fast enough and you can fix bugs, and then compile everything together
when you need the whole document)? You don't need to change a single
line if you compile separate chapters or if you compile everything
together. Except that you might need to split the document in separate
files (using projects/products is really a great thing). If you don't
want to split your document, you can also use modes:

\starttext

\startmode[everything]
\enablemode[chapter1]
\enablemode[chapter2]
\stopmode

\chapter{Introduction}

\startmode[chapter1]
\chapter{Chapter A}
\stopmode

\startmode[chapter2]
\chapter{Chapter B}
\stopmode

\stoptext

Then you can compile the document with
    texexec --mode=chapter1 filename
or
    texexec --mode=chapter1,chapter2 filename
or
    texexec --mode=everything filename

Mojca

      reply	other threads:[~2006-02-22 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 16:34 andrea valle
2006-02-21 16:59 ` Mojca Miklavec
2006-02-22 11:03   ` andrea valle
2006-02-22 15:44     ` Mojca Miklavec [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=6faad9f00602220744j593bf165tb4eb91b7ca2e4e4b@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).