aboutsummaryrefslogtreecommitdiffstats
path: root/doc/user/prg_chan
diff options
context:
space:
mode:
authorJeffrey H. Kingston <jeff@it.usyd.edu.au>2010-09-14 20:38:23 +0000
committerJeffrey H. Kingston <jeff@it.usyd.edu.au>2010-09-14 20:38:23 +0000
commit78c2bcf9e96ab00615ee6f96905bca78fcd52a00 (patch)
tree9c7e31f2a59e174433e55b589771005b48a34158 /doc/user/prg_chan
parent9daa98ce90ceeeaba9e942d28575d8fcfe36db4b (diff)
downloadlout-78c2bcf9e96ab00615ee6f96905bca78fcd52a00.tar.gz
Lout 3.27.
git-svn-id: http://svn.savannah.nongnu.org/svn/lout/trunk@23 9365b830-b601-4143-9ba8-b4a8e2c3339c
Diffstat (limited to 'doc/user/prg_chan')
-rw-r--r--doc/user/prg_chan11
1 files changed, 7 insertions, 4 deletions
diff --git a/doc/user/prg_chan b/doc/user/prg_chan
index 781e9bb..ae67eea 100644
--- a/doc/user/prg_chan
+++ b/doc/user/prg_chan
@@ -14,8 +14,11 @@ changing it.
For general information about how to make your own setup file, consult
Section {@NumberOf setup}. The options that determine the default
values are in the @Code "@Use" clause which occupies most of the setup
+programs. @RawIndex { programs }
+programs.setup @SubIndex { setup files for }
+setup.files. @RawIndex { setup files }
+setup.files.for.programs @SubIndex { for programs }
file. Here is part of the @Code "@Use" clause from {@Code cprint}:
-cprint. @Index @Code "@CPSetup"
@ID @Code @Tbl
mv { 0.5vx }
aformat { @Cell A | @Cell B | @Cell C }
@@ -96,9 +99,9 @@ symbols, including {@Code "@Box"} and {@Code "@I"}. If you want to use
these symbols here, you must include your setup file @I after
@Code "@SysInclude { doc }" or whatever, the reverse of the usual
arrangement, so that they are defined before Lout reads your setup
-file. This reversal is carried out automatically when formatting
-programs independently of any document, so you can use these symbols
-in a setup file given by a @Code { -S } command line flag.
+file. This is always done when formatting programs independently of
+any document, so you can use these symbols in a setup file given by
+a @Code { -S } command line flag.
} If you do use exotic formats, remember that in some programming languages,
comments and even strings may occupy more than one line: {@Code "@Box"},
for example, will give a logical but probably unwanted result when