mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

force use of pandoc version >= 3.1.12.2

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

1991/buzzard/index.html
+50 -71
View File
@@ -130,8 +130,8 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Sean_Barrett">Sean Barrett</a><br>
Location: <a href="../../location.html#ZZ">ZZ</a> - <em>Unknown
location</em> <br><br></li>
Location: <a href="../../location.html#ZZ">ZZ</a> - <em>Unknown location</em>
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -141,23 +141,20 @@ location</em> <br><br></li>
<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> all</span></code></pre></div>
<p>There is an <a href="#alternate-code">alternate version</a> which
might feel more at home for vi(m) users in navigation.</p>
<p>There is an <a href="#alternate-code">alternate version</a> which might feel more at home
for vi(m) users in navigation.</p>
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p>
<pre><code>STATUS: INABIAF - please **DO NOT** fix</code></pre>
<p>For more detailed information see <a
href="../../bugs.html#1991_buzzard">1991 buzzard bugs</a>.</p>
<p>For more detailed information see <a href="../../bugs.html#1991_buzzard">1991 buzzard bugs</a>.</p>
<h2 id="to-use">To use:</h2>
<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="ex">./buzzard</span></span></code></pre></div>
<h2 id="alternate-code">Alternate code:</h2>
<p>This version changes the keys <code>f</code> for forward,
<code>l</code> for left and <code>r</code> for right by default to
<code>k</code> for forward, <code>l</code> for right and <code>h</code>
for left, which is more natural for those who use vi(m). Also one can
just hit <code>q</code> followed by enter to quit the maze. It is
problematic to reconfigure the keys except by modifying the code
directly so the keys are not made a <code>-D</code> at the compiler.</p>
<p>This version changes the keys <code>f</code> for forward, <code>l</code> for left and <code>r</code> for right by
default to <code>k</code> for forward, <code>l</code> for right and <code>h</code> for left, which is more
natural for those who use vi(m). Also one can just hit <code>q</code> followed by enter to
quit the maze. It is problematic to reconfigure the keys except by modifying the
code directly so the keys are not made a <code>-D</code> at the compiler.</p>
<h3 id="alternate-build">Alternate build:</h3>
<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="fu">make</span> alt</span></code></pre></div>
<h3 id="alternate-use">Alternate use:</h3>
@@ -167,96 +164,78 @@ directly so the keys are not made a <code>-D</code> at the compiler.</p>
<p>You are invited to try to cheat, … if you can figure out how! :-)</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="how-to-play">How to play</h3>
<p>When the game starts, you are at the far end of the maze from the
exit, looking down a corridor. To move forward, type <code>f</code> and
press return. To turn 90 degrees right, type <code>r</code>; and for
left, <code>l</code>. You can put multiple commands on one line, and the
new view will be drawn after all the moves.</p>
<p>When the game starts, you are at the far end of the maze from the exit, looking
down a corridor. To move forward, type <code>f</code> and press return. To turn 90
degrees right, type <code>r</code>; and for left, <code>l</code>. You can put multiple commands on
one line, and the new view will be drawn after all the moves.</p>
<p>The game ends if you get out the exit (you’ll know it when you see
it) or when you type <code>^D</code> (EOF).</p>
<h3 id="hints-on-how-to-cheat">Hints on how to cheat</h3>
<p>You can, of course, cheat by looking at the maze map. The question
you need to ask yourself, though, is what sequence of characters marks
the place where you can escape the maze?</p>
<p>The algorithm is quite bizarre–the primary nested loop that generates
it goes top to bottom on the display, looping forward then backward from
the current position to draw the left side and then the right side.</p>
you need to ask yourself, though, is what sequence of characters
marks the place where you can escape the maze?</p>
<p>The algorithm is quite bizarre–the primary nested loop that
generates it goes top to bottom on the display, looping forward
then backward from the current position to draw the left side and
then the right side.</p>
<h3 id="advanced-usage-notes">Advanced usage notes</h3>
<p>The program can also be run from other files containing mazes. The
maze should be laid out graphically in the obvious format; newlines
separate physical rows in the maze; a space indicates a corridor, and
any other character is a wall. Tabs are also considered walls, so make
sure to convert tabs to spaces before using it.</p>
separate physical rows in the maze; a space indicates a corridor,
and any other character is a wall. Tabs are also considered walls,
so make sure to convert tabs to spaces before using it.</p>
<p>Usage:</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="ex">./buzzard</span> [filename [escape-char [start-x start-yNNN</span></code></pre></div>
<p>Filename is the name of the file containing the maze. This defaults
to <code>buzzard.c</code> or rather <code>__FILE__</code>.</p>
<p>Filename is the name of the file containing the maze. This
defaults to <code>buzzard.c</code> or rather <code>__FILE__</code>.</p>
<p>Escape-char is the character in the maze that represents the exit.
You can put more than one exit in the maze (for example, you could make
all ’!’s in the maze be exits).</p>
<p>Start-x and start-y mark the coordinates where you begin playing. Y
coordinate is down the rows in the files, X is to the right through the
characters of each line. Both X and Y begin counting from 0. The default
is start-x = 4, start-y = 5, which is needed for the buzzard.c, but
would probably be inappropriate for other mazes.</p>
You can put more than one exit in the maze (for example, you could
make all ’!’s in the maze be exits).</p>
<p>Start-x and start-y mark the coordinates where you begin playing.
Y coordinate is down the rows in the files, X is to the right
through the characters of each line. Both X and Y begin counting
from 0. The default is start-x = 4, start-y = 5, which is needed
for the buzzard.c, but would probably be inappropriate for other
mazes.</p>
<h3 id="bugs">BUGS:</h3>
<p>You can’t change that at start you’re facing down (“south”).</p>
<p>The drawing algorithm cannot handle open spaces (two successive
side-corridors with no wall between them). In fact, it cannot handle
small dog-legs properly, although the error is subtle.</p>
<p>The exit is drawn like a normal corridor from the side view; it’s
only displayed as the exit when you are facing it.</p>
<p>The exit is drawn like a normal corridor from the side view;
it’s only displayed as the exit when you are facing it.</p>
<p>Improper command line arguments are not handled nicely.</p>
<p>Mazes with openings at the edges will cause the drawing program to
reach into arbitrary parcels of memory.</p>
<p>Mazes with openings at the edges will cause the drawing program
to reach into arbitrary parcels of memory.</p>
<p>The program assumes that tabs are set to 8 characters.</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-1991buzzard"><a name="inventory"></a>Inventory for
1991/buzzard</h1>
<h1 id="inventory-for-1991buzzard"><a name="inventory"></a>Inventory for 1991/buzzard</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/1991/buzzard/buzzard.c">buzzard.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/buzzard.alt.c">buzzard.alt.c</a>
- alternative source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/buzzard.orig.c">buzzard.orig.c</a>
- original source</li>
<li><a href="1991_buzzard.tar.bz2">1991_buzzard.tar.bz2</a> - download
entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/buzzard.c">buzzard.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/buzzard.alt.c">buzzard.alt.c</a> - alternative source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/buzzard.orig.c">buzzard.orig.c</a> - original source</li>
<li><a href="1991_buzzard.tar.bz2">1991_buzzard.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/1991/buzzard/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/.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/1991/buzzard/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/.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/1991/buzzard/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1991/buzzard/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->