From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Need to compile individual components with proper numbering, etc.
Date: Sun, 18 Dec 2005 11:49:42 +0100 [thread overview]
Message-ID: <43A53EC6.3000100@elvenkind.com> (raw)
In-Reply-To: <3F6765A2-B947-4AEA-BDA3-3EA6F61FC1CE@cox.net>
David Arnold wrote:
> All,
>
> With the structure (posted below for completeness), I will need to
> compile the individual components (small chunks to post online for
> students with modems). I know this is possible, with say texexec
> section1. However, if that is section1.tex of chapter8.tex, then I will
> need the run to produce all of the correct numbering of examples,
> equations, definitions, etc. I am hoping this is possible with this
> structure. Comments?
I believe this is not possible, but I want this as well, and so
do a few other people (that I know of). If it *can* be done,
it should be documented. If not, it sohuld be put on someone's
todo list (possibly mine). I've created a collector item.
Taco
next prev parent reply other threads:[~2005-12-18 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 2:01 David Arnold
2005-12-18 10:49 ` Taco Hoekwater [this message]
2005-12-18 17:33 ` Willi Egger
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=43A53EC6.3000100@elvenkind.com \
--to=taco@elvenkind.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).