force use of pandoc version >= 3.1.12.2

The `bin/pandoc-wrapper.sh` tool will verify that the ssytem
has a recent enough version of `pandoc(1)`.

We explain why we insist on `pandoc(1)`. version >= 3.1.12.2
in comments where the $PANDOC_MIN_VERSION is set.

Added `--wrap=preserve` as a default argument to `pandoc(1)`.
While this change will impact every HTML file generated,
we believe this will improve the ability of someone to look
at the generated HTML and correlate with the original markdown.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.4.2 2024-03-17"
to "1.4.3 2024-03-18".

Performed `make www` to achieve all of the above and to generate
HTML using the new  `--wrap=preserve` `pandoc(1)` mode.
This commit is contained in:
Landon Curt Noll committed 2024-03-18 01:26:39 -07:00
1 parent 9eb7a54e9f
commit b0b212acb1
402 files changed
+37061 -55132

No files matched your search

+75 -108
View File
@@ -129,9 +129,9 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Brian_Westley">Brian
Westley</a><br> Location: <a href="../../location.html#US">US</a> -
<em>United States of America</em> (<em>United States</em>) <br><br></li>
<li>Name: <a href="../../authors.html#Brian_Westley">Brian Westley</a><br>
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -141,68 +141,60 @@ Westley</a><br> Location: <a href="../../location.html#US">US</a> -
<h2 id="to-build">To build:</h2>
<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span> alt</span></code></pre></div>
<p>We recommend that you try the alternate version first as the original
entry requires (for better display) 80 columns and 8 character tabs with
wraparound.</p>
<p>The alt code uses the same logic as the original code except that the
original code used <code>#include</code>s of files that do not exist to
generate the messages (as compiler errors) whereas the alt code uses
<code>printf(3)</code>. For the original entry see <a
href="#original-code">Original code</a> below.</p>
<p>We recommend that you try the alternate version first as the original entry
requires (for better display) 80 columns and 8 character tabs with wraparound.</p>
<p>The alt code uses the same logic as the original code except that the original
code used <code>#include</code>s of files that do not exist to generate the messages (as
compiler errors) whereas the alt code uses <code>printf(3)</code>. For the original entry
see <a href="#original-code">Original code</a> below.</p>
<h2 id="to-use">To use:</h2>
<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./westley.alt</span></span></code></pre></div>
<p>The purpose of the game is to escape the dungeon. Depending on the
compiler line you will get a different message when you run the program.
One compiler line will make you win the game (escape the dungeon) and
others will show something else.</p>
<p><em>This is independent of the previous (if there are any previous)
compiler invocations</em> specified. That means with the right compiler
invocation you can ‘win’ the game on the first go.</p>
<p>There are a variety of different <code>-D</code> flags you give to
<code>cc</code> that change the message you get. You might wish to look
at the <a href="westley.alt.c">source code</a> to get a better idea or
see below in the <a href="#try">Try</a> section for running the game
<p>The purpose of the game is to escape the dungeon. Depending on the compiler line
you will get a different message when you run the program. One compiler line
will make you win the game (escape the dungeon) and others will show something
else.</p>
<p><em>This is independent of the previous (if there are any previous) compiler
invocations</em> specified. That means with the right compiler invocation you can
‘win’ the game on the first go.</p>
<p>There are a variety of different <code>-D</code> flags you give to <code>cc</code> that change the
message you get. You might wish to look at the <a href="westley.alt.c">source code</a> to
get a better idea or see below in the <a href="#try">Try</a> section for running the game
from start to finish.</p>
<h3 id="try">Try:</h3>
<p>For something more interesting try compiling it with different
<code>cc -D</code> arguments and then run the program each time. For
example:</p>
<p>For something more interesting try compiling it with different <code>cc -D</code> arguments
and then run the program each time. For example:</p>
<div class="sourceCode" id="cb3"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Door</span> westley.alt.c <span class="at">-o</span> westley.alt <span class="kw">&amp;&amp;</span> <span class="ex">./westley.alt</span></span>
<span id="cb3-2"><a href="#cb3-2" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Drain</span> westley.alt.c <span class="at">-o</span> westley.alt <span class="kw">&amp;&amp;</span> <span class="ex">./westley.alt</span></span></code></pre></div>
<p>To see the game from start to finish, try:</p>
<div class="sourceCode" id="cb4"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./try.alt.sh</span></span></code></pre></div>
<h2 id="original-code">Original code:</h2>
<p>The purpose of the game is to escape the dungeon <strong>via the
compiler line where you get <em>messages as compiler
errors</em></strong>. Depending on the compiler line you will get
different error messages and one compiler line will make you win the
<p>The purpose of the game is to escape the dungeon <strong>via the compiler line
where you get <em>messages as compiler errors</em></strong>. Depending on the compiler line you
will get different error messages and one compiler line will make you win the
game!</p>
<p>NOTE: your terminal should be set to 80 columns, 8 character tabs,
and wraparound. The alternate code does not have this limitation and it
is for this reason that we recommend you try it first.</p>
<p>NOTE: your terminal should be set to 80 columns, 8 character tabs, and
wraparound. The alternate code does not have this limitation and it is for this
reason that we recommend you try it first.</p>
<h3 id="original-build">Original build:</h3>
<div class="sourceCode" id="cb5"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span> all</span></code></pre></div>
<p>There are a variety of different <code>-D</code> flags you can give
to <code>cc</code> that change the message you get. You might wish to
look at the <a href="westley.c">source code</a> to get a better idea or
see below in the <a href="#original-try">Original try</a> section for
<p>There are a variety of different <code>-D</code> flags you can give to <code>cc</code> that change the
message you get. You might wish to look at the <a href="westley.c">source code</a> to get a
better idea or see below in the <a href="#original-try">Original try</a> section for
running the game from start to finish.</p>
<h2 id="original-use">Original use:</h2>
<p>There is no running of this program directly as it is supposed to
fail to compile: the purpose of the game is to escape the dungeon but
depending on the compiler line you will get a different message
(<strong>as compiler errors</strong> due to <code>#include</code> files
not existing). One compiler line will make you win the game (escape the
dungeon) and others will show something else.</p>
<p><em>This is independent of the previous (if there are any previous)
compiler invocations</em> specified. That means with the right compiler
invocation you can ‘win’ the game on the first go. But unlike the <a
href="westley.alt.c">alternate code</a>, you do not run this program as
it will not compile: instead it will be compiler error messages; there
is no running the program.</p>
<p>There is no running of this program directly as it is supposed to fail to
compile: the purpose of the game is to escape the dungeon but depending on the
compiler line you will get a different message (<strong>as compiler errors</strong> due to
<code>#include</code> files not existing). One compiler line will make you win the game
(escape the dungeon) and others will show something else.</p>
<p><em>This is independent of the previous (if there are any previous) compiler
invocations</em> specified. That means with the right compiler invocation you can
‘win’ the game on the first go. But unlike the <a href="westley.alt.c">alternate code</a>,
you do not run this program as it will not compile: instead it will be compiler
error messages; there is no running the program.</p>
<h2 id="original-try">Original try:</h2>
<p>For something more interesting try compiling it with different
<code>cc -D</code> arguments:</p>
<p>For something more interesting try compiling it with different <code>cc -D</code>
arguments:</p>
<div class="sourceCode" id="cb6"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Door</span> westley.c</span>
<span id="cb6-2"><a href="#cb6-2" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Drain</span> westley.c</span></code></pre></div>
<p>To see the game from start to complete, try:</p>
@@ -213,19 +205,19 @@ is no running the program.</p>
<p>To use:</p>
<div class="sourceCode" id="cb8"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./try.sh</span></span></code></pre></div>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>This program, in accordance with the rules, compiles into a legal C
program without human intervention. However, it simply compiles into
<code>main(){}</code>, which does nothing and exits, so you don’t need
<p>This program, in accordance with the rules, compiles into a legal
C program without human intervention. However, it simply compiles
into <code>main(){}</code>, which does nothing and exits, so you don’t need
to actually compile the program.</p>
<p>This program is a simple adventure game which uses only C
preprocessor error messages (for missing <code>#include</code> files) as
output. To begin, try to compile the program with no options:</p>
<p>This program is a simple adventure game which uses only C preprocessor
error messages (for missing <code>#include</code> files) as output. To begin,
try to compile the program with no options:</p>
<div class="sourceCode" id="cb9"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> westley.c</span></code></pre></div>
<p>This will fail, producing an error message for a missing
<code>#include</code> file as the opening description. Your terminal
should be set for 80 columns, 8 character tabs, and wraparound, as there
is no way to reliably output newlines. You should see something like
this (text massaged to change wraparound to separate lines):</p>
<p>This will fail, producing an error message for a missing <code>#include</code>
file as the opening description. Your terminal should be set for
80 columns, 8 character tabs, and wraparound, as there is no way
to reliably output newlines. You should see something like this
(text massaged to change wraparound to separate lines):</p>
<pre><code> westley.c
westley.c(87) : fatal error C1024: cannot open include file &#39;
@@ -237,20 +229,18 @@ this (text massaged to change wraparound to separate lines):</p>
&#39;</code></pre>
<p>Your compiler error message will vary, but the important part is the
missing include file name, which functions as the game text.</p>
<p>To “do” things, all words must start with <code>-D</code>. For
example, to look at the door, do:</p>
<div class="sourceCode" id="cb11"><pre
class="sourceCode sh"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Door</span> prog.c</span></code></pre></div>
<p>To “do” things, all words must start with <code>-D</code>. For example, to
look at the door, do:</p>
<div class="sourceCode" id="cb11"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Door</span> prog.c</span></code></pre></div>
<p>…and you will get another error message telling you about the door.
(note: some compilers will stop after the first missing include file,
while others will continue to try compiling; the latter will repeat the
opening message each time, as if you are playing an adventure game with
“verbose” turned on).</p>
while others will continue to try compiling; the latter will repeat
the opening message each time, as if you are playing an adventure game
with “verbose” turned on).</p>
<p>The goal of the game is to escape the dungeon.</p>
<p>Here is a walk-through for the game, including a few dead-ends:</p>
<h3 id="spoiler">SPOILER</h3>
<div class="sourceCode" id="cb12"><pre
class="sourceCode sh"><code class="sourceCode bash"><span id="cb12-1"><a href="#cb12-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Door</span> westley.c</span>
<div class="sourceCode" id="cb12"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb12-1"><a href="#cb12-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Door</span> westley.c</span>
<span id="cb12-2"><a href="#cb12-2" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Drain</span> westley.c</span>
<span id="cb12-3"><a href="#cb12-3" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Dwarf</span> westley.c</span>
<span id="cb12-4"><a href="#cb12-4" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Debris</span> westley.c <span class="co"># or -Dungeon</span></span>
@@ -271,59 +261,36 @@ class="sourceCode sh"><code class="sourceCode bash"><span id="cb12-1"><a href="#
<p>Note that the game has no real state information; you can type these
commands in any order, at any time. Also note that word order is
unimportant.</p>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0
License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights
Reserved. You are free to share and adapt this file under the terms of
this license:</p>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0 License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights Reserved.
You are free to share and adapt this file under the terms of this license:</p>
<pre><code>Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</code></pre>
<p>For more information, see:
https://creativecommons.org/licenses/by-sa/4.0/</p>
<p>For more information, see: https://creativecommons.org/licenses/by-sa/4.0/</p>
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- START: this line starts content for HTML phase 22 by: bin/output-index-inventory.sh via bin/md2html.sh -->
<!-- START: this line starts content generated by: bin/output-index-inventory.sh -->
<h1 id="inventory-for-1994westley"><a name="inventory"></a>Inventory for
1994/westley</h1>
<h1 id="inventory-for-1994westley"><a name="inventory"></a>Inventory for 1994/westley</h1>
<p><a href="#top">Jump to top</a></p>
<h2 id="primary-files">Primary files</h2>
<ul>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.c">westley.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.alt.c">westley.alt.c</a>
- alternative source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.orig.c">westley.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/try.alt.sh">try.alt.sh</a>
- how to run alternative code</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/try.sh">try.sh</a>
- how to run</li>
<li><a href="1994_westley.tar.bz2">1994_westley.tar.bz2</a> - download
entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.c">westley.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.alt.c">westley.alt.c</a> - alternative source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.orig.c">westley.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/try.alt.sh">try.alt.sh</a> - how to run alternative code</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/try.sh">try.sh</a> - how to run</li>
<li><a href="1994_westley.tar.bz2">1994_westley.tar.bz2</a> - download entry source</li>
</ul>
<h2 id="secondary-files">Secondary files</h2>
<ul>
<li><a href="index.html">index.html</a> - entry home page</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/.gitignore">.gitignore</a>
- list of files that should not be committed under git</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/.gitignore">.gitignore</a> - list of files that should not be committed under git</li>
<li><a href=".path">.path</a> - directory path from top directory</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->