From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Building a Component
Date: Mon, 12 Sep 2016 14:29:40 +0200 [thread overview]
Message-ID: <57D69FB4.8000501@gmail.com> (raw)
In-Reply-To: <29878D50-61C3-4C51-91E2-8EB00FEBE4AB@stien.de>
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
> Malte Stien <mailto:malte@stien.de>
> 12. September 2016 um 13:03
> 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
Move the two lines after \startcomponent.
> \startcomponent component-1
> \starttext
You don’t need \starttext/\stoptext when you use product and component
files.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2156 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 prev parent reply other threads:[~2016-09-12 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 11:03 Malte Stien
2016-09-12 12:29 ` Wolfgang Schuster [this message]
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=57D69FB4.8000501@gmail.com \
--to=schuster.wolfgang@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).