From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Project structure light
Date: Mon, 1 Mar 2021 18:12:38 +0100 [thread overview]
Message-ID: <0e763132-3950-77da-5f49-3dee7508c114@gmail.com> (raw)
In-Reply-To: <f18a772d366f491fbf493bee19f3486a@ub.unibe.ch>
[-- Attachment #1.1: Type: text/plain, Size: 712 bytes --]
denis.maier@ub.unibe.ch schrieb am 01.03.2021 um 17:54:
>
> Hi,
>
> another question regarding project structure. I want to put each
> chapter of a book in a component or a distinct file loaded with
> \input, but I don’t want to have a full project structure. Just a main
> file and the chapters. Nevertheless, I want to load the environment
> file in each subfile. Is that possible or will that cause problems?
>
There is no problem with this method because environment files are
loaded only once, all further attempts to load the same file are ignored.
Even though replacing \input with \component can be useful because
\component doesn't generate a error when the given file doesn't exist.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2317 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2021-03-01 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 16:54 denis.maier
2021-03-01 17:07 ` Hans Hagen
2021-03-01 17:12 ` Wolfgang Schuster [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=0e763132-3950-77da-5f49-3dee7508c114@gmail.com \
--to=wolfgang.schuster.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).