53 lines
2.1 KiB
HTML
53 lines
2.1 KiB
HTML
<html>
|
|
<head>
|
|
<!-- This file has been generated by unroff 1.0, 03/21/96 19:29:41. -->
|
|
<!-- Do not edit! -->
|
|
<link rev="made" href="mailto:net@informatik.uni-bremen.de">
|
|
<title>unroff Programmer's Manual, section 2.</title>
|
|
</head><body>
|
|
<h2><a name="section2">2.</a> <tt> </tt>Where to Place Scheme Code?
|
|
</h2>
|
|
<p>
|
|
 <tt> </tt> <tt> </tt> <tt> </tt><i>unroff
|
|
</i>accepts Scheme code in a number of places.<tt> </tt>
|
|
First, several Scheme files are loaded on startup:
|
|
<dl><dt><dd>
|
|
<pre>
|
|
scm/troff.scm
|
|
scm/<i>format</i>/common.scm
|
|
scm/<i>format</i>/<i>package</i>.scm
|
|
~/.unroff
|
|
</pre>
|
|
</dl>
|
|
<p>
|
|
 <tt> </tt> <tt> </tt> <tt> </tt>The first three path names are relative to a site-specific library
|
|
directory where the files have been installed by the system
|
|
administrator.<tt> </tt>
|
|
``troff.scm'' contains definitions that are independent of the
|
|
actual output format and troff macro-package; and the
|
|
file ``.unroff'' (loaded from the caller's home directory) typically
|
|
contains Scheme code to define user-preferences and to tailor
|
|
and extend the translation rules implemented by the files loaded
|
|
from a central location.<tt> </tt>
|
|
See the
|
|
<a href="./unroff.1.html">manual page</a>
|
|
<i>unroff</i>(1)
|
|
for more information.<tt> </tt>
|
|
<p>
|
|
 <tt> </tt> <tt> </tt> <tt> </tt>Additional files with user-supplied Scheme definitions
|
|
(e.g. translation rules for user-defined macros) can be passed to
|
|
<i>unroff
|
|
</i>by mentioning them in the command line.<tt> </tt>
|
|
In general, troff input files and Scheme source files can be mixed
|
|
arbitrarily when calling
|
|
<i>unroff</i>.<tt> </tt>
|
|
Finally, Scheme code can be embedded directly in the troff documents
|
|
by means of the new ``.##'' troff request and the corresponding
|
|
extension to the ``.ig'' request as explained in the
|
|
<a href="./unroff.1.html">manual page</a>.<tt> </tt>
|
|
Such inline Scheme code is executed on-the-fly when it is encountered
|
|
by the parser while processing the document.<tt> </tt>
|
|
<p><hr>
|
|
Markup created by <em>unroff</em> 1.0, <tt> </tt> <tt> </tt>March 21, 1996, <tt> </tt> <tt> </tt>net@informatik.uni-bremen.de</body>
|
|
</html>
|