aboutsummaryrefslogtreecommitdiffstats
path: root/doc/user/typ_orga
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/typ_orga')
-rw-r--r--doc/user/typ_orga14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/user/typ_orga b/doc/user/typ_orga
index 1e9aa36..ce49851 100644
--- a/doc/user/typ_orga
+++ b/doc/user/typ_orga
@@ -91,4 +91,18 @@ file. You might also find it useful to construct your book
@I { top-down }, as computer scientists call it, laying out all the
chapters and sections as empty skeletons and filling their contents in
later.
+@PP
+When some part of your document has to be repeated, one way to avoid
+entering it twice is to place that part in a separate file and use
+@Code "@Include" in two places to include it twice. This works, but
+there are two caveats. First, it may be better to use a definition
+(Section {@NumberOf definitions}), since that gives you an object
+with a name, which you can use with confidence anywhere at all.
+Second, Lout treats @Code "@Include" in a peculiar way when it
+appears in the setup part of a document (in definitions, databases,
+and the @Code "@Use" clauses that appear within setup files): it
+reads the file as usual the first time, and silently skips it the
+other times. This is done to simplify the handling of files of
+definitions that depend on other files of definitions, as described
+in the Expert's Guide @Cite { $kingston1995lout.expert }.
@End @Section