From: David Arnold <darnold@northcoast.com>
Cc: ntg-context@ntg.nl
Subject: Fixed my project
Date: Thu, 27 Jul 2000 20:48:58 -0700 [thread overview]
Message-ID: <3.0.5.32.20000727204858.00945b70@mail.northcoast.com> (raw)
All,
I fixed my project. I had two basic problems.
1. In the product file activities.tex, relative addressing allowed Context
to find the components:
\startproduct activities
\project linalg
\component vectors/context-vectors
\component matrices/context-matrices
\stopproduct
2. My second problem came because I followed the lead provided in
co-en-03.pdf on page 7. This steered me down the wrong highway.
By reading page 5 of the same doc, I figured I needed to start each of my
component files as follows:
\startcomponent context-matrices
\project linalg
\product activities
and
\startcomponent context-vectors
\project linalg
\product activities
I can now compile the project (linalg.tex), the product (activities.tex),
and each component (context-vectors.tex and context-matrices.tex)
separately. So, a good day's work. I am using the following to compile each
of the mentioned files:
texexec --pdf --mode=letter "%N%T"
So, a pretty good day's work. Now I am going to get to work to try and
write a screen mode in environment1.tex.
However, I still have not found a solution to an earlier post. If I have
twenty components, named component1 through component20, is there a way I
can compile a single file and produce component1.pdf through
component20.pdf? I would very much like to hear the answer to this
question, as it would be a huge timesaver and a safe way of making sure a
complete set of files is updated.
-
David Arnold
College of the Redwoods
Mathematics Department
7351 Tompkins Hill Road
Eureka, CA 95501
(707) 476-4222
My Home Page
http://online.redwoods.cc.ca.us/instruct/darnold/index.htm
Ordinary Differential Equations Using Matlab
http://www.prenhall.com/books/esm_0130113816.html
reply other threads:[~2000-07-28 3:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3.0.5.32.20000727204858.00945b70@mail.northcoast.com \
--to=darnold@northcoast.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).