From: Malte Stien <malte@stien.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Building a Component
Date: Mon, 12 Sep 2016 21:03:10 +1000 [thread overview]
Message-ID: <29878D50-61C3-4C51-91E2-8EB00FEBE4AB@stien.de> (raw)
Hi all,
I am just familiarising myself with projects/products/components. I have a number of documents that all belong to a large set of Reference Manuals and so far I have built them all separately and have relied a lot on the simple \input... statement. I assume with projects/products/components I might be able to do something much smarter. Let’s see.
I get stuck quite early on, though. I have created a minimal component file ‘component-1.tex’ and when I build it, context runs into what seems to be an infinite recursion. Here is the file:
\project test-project
\product reference-manual-1
\startcomponent component-1
\starttext
\section[c1-s1]{Component 1 Section 1}
This is a paragraph in Component 1 Section 1
\stoptext
\stopcomponent
...and here is the console when I run it:
> context component-1.tex
...
...
...
open source > 196 > 198 > component-1.tex
open source > 197 > 199 > reference-manual-1.tex
open source > 198 > 200 > component-1.tex
open source > 199 > 201 > reference-manual-1.tex
open source > 200 > 202 > component-1.tex
open source > 201 > 203 > reference-manual-1.tex
tex error > tex error on line 2 in file reference-manual-1.tex: ! TeX capacity exceeded, sorry [text input levels=600]
\m_syst_action_nop #1 ->\clf_startproduct {#1}
l.11 \startproduct reference-manual-1
1 % \project test-project
2 >> \startproduct reference-manual-1
3
4 \component component-1
5
6 \stopproduct
7
Here is reference-manual-1.tex:
\project test-project
\startproduct reference-manual-1
\component component-1
\stopproduct
This is with the latest context downloaded today. All I really know about this is from here http://wiki.contextgarden.net/Project_structure; anything else I should be reading?
Any ideas? Thank you,
Malte.
--
“The Electric Monk was a labour-saving device, like a dishwasher or a video recorder... Electric Monks believed things for you, thus saving you what was becoming an increasingly onerous task, that of believing all the things the world expected you to believe. ― Douglas Adams, Dirk Gently's Holistic Detective Agency
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2016-09-12 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 11:03 Malte Stien [this message]
2016-09-12 12:29 ` Wolfgang Schuster
2016-09-12 23:28 ` Malte Stien
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=29878D50-61C3-4C51-91E2-8EB00FEBE4AB@stien.de \
--to=malte@stien.de \
--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).