Changeset 15144 in project


Ignore:
Timestamp:
07/03/09 12:13:07 (11 years ago)
Author:
Ivan Raikov
Message:

improvements of mistie installation

Location:
release/4/mistie
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • release/4/mistie/mistie.html

    r296 r15144  
    11<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    2 <!-- Generated by eggdoc Revision: 1.17  -->
     2<!-- Generated by eggdoc Revision: 1.20  -->
    33<html>
    44<head>
    5 <title>Eggs Unlimited - mistie</title><style type="text/css"> <!--
    6       CODE {
    7             color: #666666;
    8           }
    9 /*   DT.definition EM { font-weight: bold; font-style: normal; } */
    10 
    11      DT.definition {
    12                    background: #eee;
     5<title>Eggs Unlimited - mistie</title><style type="text/css"><!--
     6       CODE {
     7             color: #666666;
     8           }
     9 /*   DT.definition EM { font-weight: bold; font-style: normal; } */
     10;      DT.definition {
     11                    background: #eee;
    1312                   color: black;
    1413                   padding: 0.2em 1em 0.2em 0.7em;
     
    2625                    border-top: 1px solid #448;
    2726                    padding-left: 1em;
    28      }
     27                    margin-bottom: 1.2em;
     28     }
     29     DIV.subsubsection {
     30                    border-top: 1px dotted #99c;
     31                    /* border-left: 1px solid #99c; */
     32                    padding-left: 1em;
     33                    margin-bottom: 1.2em;
     34     }
     35     DIV.subsubsubsection {
     36                    border-top: 1px solid #ddf;
     37                    padding-left: 1em;
     38                    margin-bottom: 1.2em;
     39     }
     40
    2941         DIV.section {
    3042                 margin-bottom: 1.5em;
     
    4557                 margin: 0 0 1em 0;
    4658        }
    47         LI {
     59        UL LI {
    4860                list-style: none;
    4961        }
     
    5668                margin-bottom: 0.5em;
    5769        }
     70        H4, H5, H6 {
     71                color: #113;
     72                margin-bottom: 1.0em;
     73        }
     74        H5 {
     75                font-weight: normal;
     76                font-style: italic;
     77                font-size: 100%;
     78                margin-top: 1.2em;
     79        }
     80        H6 {
     81                font-weight: bold;
     82                font-size: 85%;
     83                margin-top: 1.2em;
     84        }
    5885     DIV#eggheader {
    5986         text-align: center;
     
    101128       padding: 0.2em;
    102129       border: 1px solid #aac;
     130       border-collapse: collapse;
    103131       width: 100%;
    104132     }
     
    109137     }
    110138     TH {
    111        border-bottom: 1px solid black;
    112      } --></style></head>
     139       text-align: left;
     140       border-bottom: 1px solid #aac;
     141       padding: 0.25em 0.5em 0.25em 0.5em;
     142     }
     143     TD { padding: 0.25em 0.5em 0.25em 0.5em; }
     144     --></style></head>
    113145<body>
    114146<div id="header">
    115147<h2>mistie</h2>
    116 <div id="eggheader">
    117 <a href="index.html">
     148<div id="eggheader"><a href="index.html">
    118149<img src="egg.jpg" alt="[Picture of an egg]" /></a></div></div>
    119150<div id="body">
     
    128159<li>1.0 Initial release</li></ul></div>
    129160<div class="section">
    130 <h3>Usage</h3>
    131 <tt>(require-extension mistie)</tt></div>
     161<h3>Usage</h3><tt>(require-extension mistie)</tt></div>
    132162<div class="section">
    133 <h3>Download</h3>
    134 <a href="mistie.egg">mistie.egg</a></div>
     163<h3>Download</h3><a href="mistie.egg">mistie.egg</a></div>
    135164<div class="section">
    136165<h3>Documentation</h3>
     
    139168
    140169
    141 <h3>
    142 <span class="subject">Mistie</span></h3>
     170<h3><span class="subject">Mistie</span></h3>
    143171
    144172</p>
     
    165193<p>
    166194
    167 produces an
    168 <code>output.doc</code> that is indistinguishable
    169 from
    170 <code>input.doc</code>. 
    171 <tt>mistie-main</tt> can be given a
     195produces an <code>output.doc</code> that is indistinguishable
     196from <code>input.doc</code>.  <tt>mistie-main</tt> can be given a
    172197file's name as argument, in which  case it reads
    173198that file instead of standard input.  Thus, the above
     
    185210To make Mistie do something more interesting than
    186211copying input verbatim to output, the user must supply
    187 a
    188 <em>format file</em>.  A format file is a Scheme file
     212a <em>format file</em>.  A format file is a Scheme file
    189213that describes the markup of the input document
    190214in terms of the desired output format.  Format files
    191 are normal Scheme files and can be loaded with
    192 <tt>mistie-load</tt>. E.g.,
     215are normal Scheme files and can be loaded with <tt>mistie-load</tt>. E.g.,
    193216</p>
    194217<p>
     
    201224<p>
    202225
    203 produces a formatted version of
    204 <code>input.doc</code>,
     226produces a formatted version of <code>input.doc</code>,
    205227the formatting being dictated by the format file
    206 
    207228<code>myformat.mistie</code>.  The formatted version may either
    208229go to standard output or to some file depending on
    209 
    210 <code>myformat.mistie</code>.  We will use the
    211 <code>.mistie</code>
     230<code>myformat.mistie</code>.  We will use the <code>.mistie</code>
    212231extension for Scheme files used as format files,
    213232but this is just a convention.
     
    218237infrastructure to define a particular markup, deciding
    219238both what the input document should look like and what
    220 kind of output to emit.  Format authors are
    221 <em>not</em>
     239kind of output to emit.  Format authors are <em>not</em>
    222240limited to a specialized sublanguage -- they can use
    223241full Scheme, including all the nonstandard features
     
    244262The distribution includes several sample format
    245263files: Format files may be combined in the call to
    246 
    247264<code>mistie.scm</code>, e.g.,
    248265</p>
     
    259276Alternatively, a new combination format file can
    260277be written that loads other format files.  E.g.,
    261 the following format file
    262 <code>basic.mistie</code> combines
    263 within itself the effects of
    264 <code>plain.mistie</code>,
    265 
    266 <code>scmhilit.mistie</code>, and
    267 <code>multipage.mistie</code>:
     278the following format file <code>basic.mistie</code> combines
     279within itself the effects of <code>plain.mistie</code>,
     280<code>scmhilit.mistie</code>, and <code>multipage.mistie</code>:
    268281</p>
    269282<p>
     
    291304<p>
    292305
    293 Note that the format file
    294 <code>multipage.mistie</code> creates
    295 a set of
    296 <code>.html</code> files whose names are based on
     306Note that the format file <code>multipage.mistie</code> creates
     307a set of <code>.html</code> files whose names are based on
    297308the name of the input document.  Therefore, when
    298309using this format file, whether explicitly or
     
    304315The name Mistie stands for Markup In Scheme That
    305316Is Extensible.  Possible pronunciations are
    306 
    307 <em>miss-tea</em> and
    308 <em>miss-tie</em>.
    309 </p>
    310 <p>
    311 
     317<em>miss-tea</em> and <em>miss-tie</em>.
     318</p>
     319<p>
    312320
    313321<a>
     
    318326trigger non-trivial changes in the output document.
    319327E.g., if the output is to be HTML, we'd like the
    320 characters
    321 <code>&lt;</code>,
    322 <code>&gt;</code>,
    323 <code>&amp;</code>, and
    324 <code>&quot;</code> in the
    325 input to come out as
    326 <code>&amp;lt;</code>,
    327 <code>&amp;gt;</code>,
    328 <code>&amp;amp;</code>,
    329 and
    330 <code>&amp;quot;</code>, respectively.  The Mistie
    331 procedure
    332 <code>mistie-def-char</code>  can be used for this:
     328characters <code>&lt;</code>, <code>&gt;</code>, <code>&amp;</code>, and <code>&quot;</code> in the
     329input to come out as <code>&amp;lt;</code>, <code>&amp;gt;</code>, <code>&amp;amp;</code>,
     330and <code>&amp;quot;</code>, respectively.  The Mistie
     331procedure <code>mistie-def-char</code>  can be used for this:
    333332</a></p>
    334333<p>
     
    354353</p>
    355354<p>
    356 
    357355
    358356<code>mistie-def-char</code> takes two arguments:  The first is
     
    365363Suppose we want a contiguous sequence of blank lines
    366364to be come out as the paragraph separator,
    367 
    368 <code>&lt;p&gt;</code>.  We could
    369 <code>mistie-def-char</code> the newline
     365<code>&lt;p&gt;</code>.  We could <code>mistie-def-char</code> the newline
    370366character as follows:
    371367</p>
     
    391387newlines it picked up.  If there was at least one,
    392388it outputs the paragraph separator, viz.,
    393 
    394389<code>&lt;p&gt;</code> followed by two newlines (added for human
    395390readability).  Otherwise, it merely prints the
    396391picked up whitespace as is.  The help procedures
    397 
    398 <code>h-read-whitespace</code> and
    399 <code>h-number-of-newlines</code>
     392<code>h-read-whitespace</code> and <code>h-number-of-newlines</code>
    400393are ordinary Scheme procedures:
    401394</p>
     
    424417<p>
    425418
    426 
    427419<a>
    428420<h3>1.1 Control sequences</h3>
    429421
    430 The Mistie procedure
    431 <code>mistie-def-ctl-seq</code> defines
    432 
     422The Mistie procedure <code>mistie-def-ctl-seq</code> defines
    433423<em>control sequences</em>.  A control sequence is a
    434424sequence of letters (alphabetic characters), and
    435425is invoked in the input document by prefixing the
    436 sequence with an
    437 <em>escape character</em>.  (The case of
    438 the letters is insignificant.) 
    439 <code>mistie-def-ctl-seq</code>
     426sequence with an <em>escape character</em>.  (The case of
     427the letters is insignificant.)  <code>mistie-def-ctl-seq</code>
    440428associates a procedure with a control sequence --
    441429when the control sequence occurs in the input
    442430document, it causes the procedure to be applied.
    443 The following defines the control sequence
    444 <code>br</code>,
    445 which emits the HTML tag
    446 <code>&lt;br&gt;</code>:
     431The following defines the control sequence <code>br</code>,
     432which emits the HTML tag <code>&lt;br&gt;</code>:
    447433</a></p>
    448434<p>
     
    469455<p>
    470456
    471 We can now invoke the
    472 <code>br</code> control sequence as
    473 <code>\br</code>.
    474 </p>
    475 <p>
    476 
     457We can now invoke the <code>br</code> control sequence as <code>\br</code>.
     458</p>
     459<p>
    477460
    478461<a>
     
    481464However, we can do better and get automatic line
    482465breaks with a more powerful control sequence.  Let's
    483 say text between
    484 <code>\obeylines</code> and
    485 <code>\endobeylines</code>
     466say text between <code>\obeylines</code> and <code>\endobeylines</code>
    486467should have automatic line breaks.  We define
    487 the control sequences
    488 <code>obeylines</code> and
    489 
     468the control sequences <code>obeylines</code> and
    490469<code>endobeylines</code> as follows:
    491470</a></p>
     
    508487<p>
    509488
    510 The
    511 <code>obeylines</code> control sequence first pushes a new
     489The <code>obeylines</code> control sequence first pushes a new
    512490frame on to the Mistie environment, using the Mistie
    513 procedure
    514 <code>mistie-push-frame</code>.  What this means is
    515 that any definitions (whether
    516 <code>mistie-def-char</code> or
    517 
     491procedure <code>mistie-push-frame</code>.  What this means is
     492that any definitions (whether <code>mistie-def-char</code> or
    518493<code>mistie-def-ctl-seq</code>) will shadow existing
    519494definitions.  The Mistie procedure
    520 
    521495<code>mistie-pop-frame</code> exits the frame, causing
    522496the older definitions to take effect again.
     
    525499
    526500In this case, we create a shadowing
    527 
    528501<code>mistie-def-char</code> for newline, so that it will emit
    529 
    530502<code>&lt;br&gt;</code> instead of performing its default action
    531503(which, as we described above, was to look for
    532504paragraph separation).  We also define a control
    533 sequence
    534 <code>endobeylines</code> which will pop the frame
    535 pushed by
    536 <code>obeylines</code>.  With this definition in
    537 place, any text sandwiched between
    538 <code>\obeylines</code> and
    539 
    540 <code>\endobeylines</code> (assuming
    541 <code>\</code> is the escape
    542 character) will be output with a
    543 <code>&lt;br&gt;</code> at the end
     505sequence <code>endobeylines</code> which will pop the frame
     506pushed by <code>obeylines</code>.  With this definition in
     507place, any text sandwiched between <code>\obeylines</code> and
     508<code>\endobeylines</code> (assuming <code>\</code> is the escape
     509character) will be output with a <code>&lt;br&gt;</code> at the end
    544510of each of its lines.
    545511</p>
    546512<p>
    547513
    548 
    549514<a>
    550515<h3>1.3 Calling Scheme from within the document</h3>
    551516
    552 We can define a control sequence
    553 <code>eval</code> that
     517We can define a control sequence <code>eval</code> that
    554518will allow the input document to explicitly evaluate
    555519Scheme expressions, without having to put them all
     
    567531<p>
    568532
    569 This will cause
    570 <code>\eval</code> followed by a Scheme
     533This will cause <code>\eval</code> followed by a Scheme
    571534expression to evaluate that Scheme expression.
    572535E.g.,
     
    581544<p>
    582545
    583 will cause
    584 <code>42</code> to be printed at the point where the
    585 
     546will cause <code>42</code> to be printed at the point where the
    586547<code>\eval</code> statement is placed.  Of course, once you
    587548have arbitrary access to Scheme within your document,
    588549the amount of kooky intertextual stuff you can do is
    589550limited only by your imagination.  A mundane use for
    590 
    591551<code>\eval</code> is to  reset the escape character at
    592552arbitrary locations in the document, should the
     
    595555</p>
    596556<h3>1.4 Utilities</h3>
    597 <p>To load a
    598 <tt>mistie</tt> file, you should use the
    599 <tt>(mistie-load FILENAME ...)</tt> procedure, which will search the working directory and the directory given in the parameter
    600 <tt>mistie-path</tt> (which defaults to the value of
    601 <tt>(repository-path)</tt>, the path where
    602 <tt>chicken-setup</tt> will install the initially provided
    603 <tt>.mistie</tt> files).</p>
    604 <p>
    605 <tt>(mistie-main [FILENAME])</tt> will invoke the filtering process.</p>
    606 <p>
    607 
     557<p>To load a <tt>mistie</tt> file, you should use the <tt>(mistie-load FILENAME ...)</tt> procedure, which will search the working directory and the directory given in the parameter <tt>mistie-path</tt> (which defaults to the value of <tt>(repository-path)</tt>, the path where <tt>chicken-setup</tt> will install the initially provided <tt>.mistie</tt> files).</p>
     558<p><tt>(mistie-main [FILENAME])</tt> will invoke the filtering process.</p>
     559<p>
    608560
    609561<a>
     
    615567<p>
    616568
    617 
    618569<a>
    619570<h3>2.1 plain.mistie</h3>
    620 
    621571
    622572<code>plain.mistie</code> is a basic format file.  It specifies
     
    632582<p>
    633583
    634 
    635 <code>plain</code> converts the characters
    636 <code>&lt;</code>,
    637 <code>&gt;</code>,
    638 <code>&amp;</code>,
    639 and
    640 <code>&quot;</code> to their HTML encodings.  One or more blank
     584<code>plain</code> converts the characters <code>&lt;</code>, <code>&gt;</code>, <code>&amp;</code>,
     585and <code>&quot;</code> to their HTML encodings.  One or more blank
    641586lines are treated as paragraph separation.
    642587</p>
    643588<p>
    644 
    645589
    646590<code>plain</code> provides a small set of control sequences
    647591geared for manual writing.  The default escape
    648 character is
    649 <code>\</code> (backslash).  Typically,
    650 
    651 <em>arguments</em> of
    652 <code>plain</code>'s control sequences are
    653 specified within braces (
    654 <code>{...}</code>), as in TeX or
     592character is <code>\</code> (backslash).  Typically,
     593<em>arguments</em> of <code>plain</code>'s control sequences are
     594specified within braces (<code>{...}</code>), as in TeX or
    655595LaTeX.
    656596</p>
    657597<p>
    658598
    659 
    660599<code>\i</code> typesets its argument in italic.  E.g.,
    661 
    662 <code>\i{italic}</code> produces
    663 <em>italic</em>.   Other control
    664 sequences in this vein are
    665 <code>\b</code> for bold and
    666 
     600<code>\i{italic}</code> produces <em>italic</em>.   Other control
     601sequences in this vein are <code>\b</code> for bold and
    667602<code>\small</code> for small print.
    668603</p>
    669604<p>
    670 
    671605
    672606<code>\p</code> puts its argument in monospace fixed font
    673607and is used for program code.  If it is not
    674 convenient to enclose
    675 <code>\p</code>'s argument in braces
     608convenient to enclose <code>\p</code>'s argument in braces
    676609(e.g., the enclosed code contains non-matching
    677610braces), then the argument may be specified by the
    678611placing the same character on each side.   (This is
    679 like LaTeX's
    680 <code>\verb</code>.)  Another useful feature of
    681 the
    682 <code>\p</code> control sequence:  If its argument starts
     612like LaTeX's <code>\verb</code>.)  Another useful feature of
     613the <code>\p</code> control sequence:  If its argument starts
    683614with a newline, it is displayed with the linebreaks
    684615preserved.
     
    686617<p>
    687618
    688 Use
    689 <code>\title</code> for specifying a document's
     619Use <code>\title</code> for specifying a document's
    690620title, which is used as both the internal title
    691621and the external (bookmarkable) title.
     
    693623<p>
    694624
    695 
    696625<code>\stylesheet{file.css}</code> causes the resulting
    697 HTML file to use the file
    698 <code>file.css</code> as its  style
    699 sheet.  A sample style sheet
    700 <code>mistie.css</code> is
     626HTML file to use the file <code>file.css</code> as its  style
     627sheet.  A sample style sheet <code>mistie.css</code> is
    701628included in the distribution.
    702629</p>
    703630<p>
    704631
    705 
    706 <code>\section</code>,
    707 <code>\subsection</code>,
    708 <code>\subsubsection</code>
     632<code>\section</code>, <code>\subsection</code>, <code>\subsubsection</code>
    709633produce numbered section headers of the
    710 appropriate depth. 
    711 <code>\section*</code>, etc., produce
     634appropriate depth.  <code>\section*</code>, etc., produce
    712635unnumbered sections.
    713636</p>
    714637<p>
    715638
    716 
    717639<code>\urlh{URL}{TEXT}</code> typesets TEXT as a link to URL.
    718640</p>
    719641<p>
    720 
    721642
    722643<code>\obeylines{...}</code> preserves linebreaks for its argument.
    723644Note that this is dissimilar in call, though not in
    724 function, to TeX's
    725 <code>{\obeylines ...}</code>.
    726 </p>
    727 <p>
    728 
    729 
    730 <code>\flushright</code> is like
    731 <code>\obeylines</code>, but sets its argument
     645function, to TeX's <code>{\obeylines ...}</code>.
     646</p>
     647<p>
     648
     649<code>\flushright</code> is like <code>\obeylines</code>, but sets its argument
    732650lines flush right.
    733651</p>
    734652<p>
    735653
    736 
    737 <code>\input FILE</code> or
    738 <code>\input{FILE}</code> includes the
    739 contents of
    740 <code>FILE</code>.
    741 </p>
    742 <p>
    743 
     654<code>\input FILE</code> or <code>\input{FILE}</code> includes the
     655contents of <code>FILE</code>.
     656</p>
     657<p>
    744658
    745659<code>\eval</code> evaluates the following Scheme expression.
     
    747661<p>
    748662
    749 
    750663<a>
    751664<h3>2.2 footnote.mistie</h3>
    752665
    753 This format supplies the
    754 <code>\footnote</code> control
     666This format supplies the <code>\footnote</code> control
    755667sequence, which makes a footnote out of its
    756668(brace-delimited) argument.  Footnotes are numbered
     
    760672<p>
    761673
    762 
    763674<a>
    764675<h3>2.3 scmhilit.mistie</h3>
    765676
    766 This format provides the
    767 <code>\q</code> control sequence which
    768 is used exactly like
    769 <code>\p</code>, except that it
    770 syntax-highlights the enclosed code.  (
    771 <code>q</code> is
    772 <code>p</code>
     677This format provides the <code>\q</code> control sequence which
     678is used exactly like <code>\p</code>, except that it
     679syntax-highlights the enclosed code.  (<code>q</code> is <code>p</code>
    773680with a twist.) Used for Scheme and Common Lisp code.
    774 
    775681<code>scmhilit</code> distinguishes between syntactic
    776682keywords (i.e., special forms and macros);
     
    778684characters; numbers; strings; comments; and background
    779685punctuation.  You can add your own keywords and
    780 constants with
    781 <code>\scmkeyword</code> and
    782 <code>\scmconstant</code>,
     686constants with <code>\scmkeyword</code> and <code>\scmconstant</code>,
    783687e.g.,
    784688</a></p>
     
    794698<p>
    795699
    796 A style sheet (see
    797 <code>plain.mistie</code>) is used to
    798 set the colors.  The style sheet
    799 <code>mistie.css</code>,
     700A style sheet (see <code>plain.mistie</code>) is used to
     701set the colors.  The style sheet <code>mistie.css</code>,
    800702provided with this distribution, has the following
    801 
    802703<em>style class</em> settings:
    803704</p>
     
    830731<p>
    831732
    832 The class
    833 <code>.scheme</code> specifies the background
     733The class <code>.scheme</code> specifies the background
    834734punctuation style, and the various subclasses,
    835 --
    836 <code>.keyword</code>,
    837 <code>.variable</code>, etc. -- specify the
     735-- <code>.keyword</code>, <code>.variable</code>, etc. -- specify the
    838736styles for the various syntactic categories.  Note
    839737that we have combined the subclasses for numbers,
     
    850748<p>
    851749
    852 
    853750<a>
    854751<h3>2.4 multipage.mistie</h3>
    855752
    856 This format provides the
    857 <code>\pagebreak</code> control
     753This format provides the <code>\pagebreak</code> control
    858754sequence, which causes a fresh HTML page to used for
    859755subsequent text.  The names of the HTML pages depend
     
    869765<p>
    870766
    871 
    872767<a>
    873768<h3>2.5 xref.mistie</h3>
    874769
    875 This provides LaTeX-like cross-references. 
    876 <code>\label{LABEL}</code>
    877 associates
    878 <code>LABEL</code> with the nearest section (or footnote)
    879 number. 
    880 <code>\ref{LABEL}</code> prints the number associated with
    881 
     770This provides LaTeX-like cross-references.  <code>\label{LABEL}</code>
     771associates <code>LABEL</code> with the nearest section (or footnote)
     772number.  <code>\ref{LABEL}</code> prints the number associated with
    882773<code>LABEL</code>.
    883774</a></p>
    884775<p>
    885776
    886 
    887777<code>\bibitem</code> can be used to enumerate bibliographic entries.
    888 
    889778<code>\cite{BIBKEY}</code> points to the entry introduced by
    890 
    891 <code>\bibitem{BIBKEY}</code>. 
    892 <code>\cite</code>'s argument can list multiple
     779<code>\bibitem{BIBKEY}</code>.  <code>\cite</code>'s argument can list multiple
    893780keys, with comma as the separator.
    894781</p>
    895782<p>
    896 
    897783
    898784<a>
     
    925811OTHER DEALINGS IN THE SOFTWARE.</pre></div></div>
    926812<div id="footer">
    927 <hr />
    928 <a href="index.html">&lt; Egg index</a>
     813<hr /><a href="index.html">&lt; Egg index</a>
    929814<div id="revision-history">$Revision$ $Date$</div>&nbsp;</div></body></html>
  • release/4/mistie/mistie.meta

    r299 r15144  
    1010        "formats.doc" "mistie.doc" "multipage.mistie" "scmhilit.mistie" "plain.mistie"
    1111        "timestamp.mistie" "xref.mistie")
     12 
     13 (needs eggdoc)
     14 (eggdoc "doc.scm")
     15
    1216)
    1317
  • release/4/mistie/mistie.setup

    r14624 r15144  
     1;;;; -*- Hen -*-
    12
    2 (compile -s -O2 -d1 -j mistie mistie.scm)
    3 (compile -s -O2 -d1 mistie.import.scm)
     3(define (dynld-name fn)         
     4  (make-pathname #f fn ##sys#load-dynamic-extension))   
     5
     6(compile -O2 -d0 -s mistie.scm -j mistie)
     7(compile -O2 -d0 -s mistie.import.scm)
     8
     9(run (csi -s doc.scm > mistie.html))
    410
    511(install-extension
    6  'mistie
    7  '("mistie.so"
    8    "mistie.import.so"
    9    "basic.mistie"
    10    "footnote.mistie"
    11    "multipage.mistie"
    12    "plain.mistie"
    13    "scmhilit.mistie"
    14    "timestamp.mistie"
    15    "xref.mistie"
    16    "mistie.html")
    17  '((version 1.2)))
     12
     13  ; Name of your extension:
     14  'digraph
     15
     16  ; Files to install for your extension:
     17  `(,(dynld-name "mistie") ,(dynld-name "mistie.import") )
     18
     19  ; Assoc list with properties for your extension:
     20  `((version 1.3)
     21    (documentation "mistie.html")
     22    ))
     23
     24
     25;; From setup-header.scm by Kon Lovett
     26
     27;;; Constants & Procedures
     28
     29(define SHARED-DIR (chicken-home))
     30
     31(define MISTIE-DIR (make-pathname SHARED-DIR "mistie"))
     32
     33
     34;; File Copy Operations
     35
     36(define (*file-copy fn dn)
     37  (let ([fn (->string fn)])
     38    (copy-file fn (make-pathname dn fn)) ) )
     39
     40(define (copy-to-shared fn)
     41  (*file-copy (->string fn) (chicken-home)) )
     42
     43(define (copy-file-to-mistie-dir fn)
     44  (*file-copy (->string fn) MISTIE-DIR) )
     45
     46(if (not (file-exists? MISTIE-DIR))
     47    (create-directory MISTIE-DIR))
     48
     49(for-each (lambda (x) (copy-file-to-mistie-dir x))
     50          (list "basic.mistie"
     51                "footnote.mistie"
     52                "multipage.mistie"
     53                "plain.mistie"
     54                "scmhilit.mistie"
     55                "timestamp.mistie"
     56                "xref.mistie"))
     57
     58         
     59
Note: See TracChangeset for help on using the changeset viewer.