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:
1 parent
9eb7a54e9f
commit
b0b212acb1
402 files changed
+37061
-55132
No files matched your search
+70
-100
@@ -129,9 +129,9 @@
|
||||
|
||||
<h2 id="author"><a name="author"></a>Author:</h2>
|
||||
<ul>
|
||||
<li>Name: <a href="../../authors.html#Mark_Schnitzius">Mark
|
||||
Schnitzius</a><br> Location: <a href="../../location.html#ZZ">ZZ</a> -
|
||||
<em>Unknown location</em> <br><br></li>
|
||||
<li>Name: <a href="../../authors.html#Mark_Schnitzius">Mark Schnitzius</a><br>
|
||||
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 -->
|
||||
@@ -145,84 +145,76 @@ Schnitzius</a><br> Location: <a href="../../location.html#ZZ">ZZ</a> -
|
||||
<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">./schnitzi</span> <span class="op"><</span>foo <span class="kw">|</span> <span class="fu">vi</span> <span class="at">-n</span></span></code></pre></div>
|
||||
<h2 id="try">Try:</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">./try.sh</span></span></code></pre></div>
|
||||
<p>NOTE: if you’re one of those who don’t know how to exit
|
||||
<code>vi</code> :-) don’t worry as it will exit for you.</p>
|
||||
<p>NOTE: if you’re one of those who don’t know how to exit <code>vi</code> :-) don’t worry as
|
||||
it will exit for you.</p>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>This exemplifies the meaning of Visual Editor, but we don’t think
|
||||
that any benchmarking sites are going to use this to tout the
|
||||
performance of the latest hardware!</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<p>If you’ve ever pasted a large chunk of text into an editor (such as
|
||||
<code>vi</code>) without first putting it into insert mode, or turning
|
||||
off the auto-indent, you know the dismay of watching your screen fill up
|
||||
with misaligned junk.</p>
|
||||
<p>It’s not the editor’s fault. The editor is just acting just as if you
|
||||
typed exactly what you’re pasting. (Of course, you could blame the
|
||||
editor for being modal in the first place, but that’s a discussion for
|
||||
another time.)</p>
|
||||
<p>It occurred to me that you could get interesting results by pasting a
|
||||
carefully designed string into the editor. In fact, if the pasted string
|
||||
contains cursor navigation commands, you can go back and overwrite
|
||||
things that were already inserted earlier in string, anywhere on the
|
||||
screen. Can you see where this is going?</p>
|
||||
<code>vi</code>) without first putting it into insert mode, or turning off
|
||||
the auto-indent, you know the dismay of watching your screen fill
|
||||
up with misaligned junk.</p>
|
||||
<p>It’s not the editor’s fault. The editor is just acting just as if
|
||||
you typed exactly what you’re pasting. (Of course, you could blame
|
||||
the editor for being modal in the first place, but that’s a
|
||||
discussion for another time.)</p>
|
||||
<p>It occurred to me that you could get interesting results by pasting
|
||||
a carefully designed string into the editor. In fact, if the pasted
|
||||
string contains cursor navigation commands, you can go back and
|
||||
overwrite things that were already inserted earlier in string,
|
||||
anywhere on the screen. Can you see where this is going?</p>
|
||||
<h3 id="animation">ANIMATION!</h3>
|
||||
<p>The program takes input from <code>stdin</code> which defines the
|
||||
animated elements (sprites) that appear on the screen. For each sprite,
|
||||
<p>The program takes input from <code>stdin</code> which defines the animated
|
||||
elements (sprites) that appear on the screen. For each sprite,
|
||||
you can specify exactly when and how long it will appear, and which
|
||||
direction it is moving. Also, the sprite can oscillate between up to
|
||||
four different views, which appear in subsequent frames. Forgive me,
|
||||
animators, if I’m mangling the terminology. Sprites which appear later
|
||||
in the input file will be drawn in front of sprites which appear
|
||||
earlier.</p>
|
||||
<p>The output, written to <code>stdout</code>, is a string which, when
|
||||
pasted into vi, will perform the animation defined in the input. (The vi
|
||||
editor is a common (and ancient) editor that should be available on most
|
||||
Unix, Linux, Solaris, and macOS systems; you can get it on Windows by
|
||||
installing Cygwin, which is how I do it.)</p>
|
||||
direction it is moving. Also, the sprite can oscillate between
|
||||
up to four different views, which appear in subsequent frames.
|
||||
Forgive me, animators, if I’m mangling the terminology. Sprites
|
||||
which appear later in the input file will be drawn in front of
|
||||
sprites which appear earlier.</p>
|
||||
<p>The output, written to <code>stdout</code>, is a string which, when pasted into vi, will
|
||||
perform the animation defined in the input. (The vi editor is a common (and
|
||||
ancient) editor that should be available on most Unix, Linux, Solaris, and macOS
|
||||
systems; you can get it on Windows by installing Cygwin, which is how I do
|
||||
it.)</p>
|
||||
<h3 id="the-input">THE INPUT</h3>
|
||||
<p>It’s easiest to place the input in a file, so you can redirect it to
|
||||
<code>stdin</code> when running the program. What follows is a detailed
|
||||
<p>It’s easiest to place the input in a file, so you can redirect it
|
||||
to <code>stdin</code> when running the program. What follows is a detailed
|
||||
description of the input file format.</p>
|
||||
<p>The first line is specified thusly:</p>
|
||||
<pre><code>[duration] [timefactor]</code></pre>
|
||||
<p>The first parameter, <code>duration</code>, defines how long the
|
||||
animation will run. The second, <code>timefactor</code>, is used as sort
|
||||
of a fudge factor for machines that run too fast to see the animation. A
|
||||
<code>timefactor</code> of 0 means, “run the animation as fast as you
|
||||
can”. On a pretty fast machine, I’ve had to set it as high as 2000 to
|
||||
get the animation to slow down sufficiently. Note that the higher the
|
||||
<code>timefactor</code>, the longer the output string that you’ll have
|
||||
to copy and paste, as extra characters are necessary to “waste time”
|
||||
between frames.</p>
|
||||
<p>The first parameter, <code>duration</code>, defines how long the animation will run. The
|
||||
second, <code>timefactor</code>, is used as sort of a fudge factor for machines that run
|
||||
too fast to see the animation. A <code>timefactor</code> of 0 means, “run the animation as
|
||||
fast as you can”. On a pretty fast machine, I’ve had to set it as high as 2000
|
||||
to get the animation to slow down sufficiently. Note that the higher the
|
||||
<code>timefactor</code>, the longer the output string that you’ll have to copy and paste,
|
||||
as extra characters are necessary to “waste time” between frames.</p>
|
||||
<p>Following the first line parameters, you may have up to nine
|
||||
different sprites, each up 50 by 50 in size, and with up to four
|
||||
different ‘views’ of that object, which are cycled through with each
|
||||
successive frame. Each sprite begins with a line of parameters of the
|
||||
following form:</p>
|
||||
different ‘views’ of that object, which are cycled through with
|
||||
each successive frame. Each sprite begins with a line of parameters
|
||||
of the following form:</p>
|
||||
<pre><code>[start] [end] [x] [y] [dx] [dy] [cols] [rows] [viewcount]</code></pre>
|
||||
<p>where:</p>
|
||||
<ul>
|
||||
<li><p><code>start</code> is the time at which this sprite first
|
||||
appears.</p></li>
|
||||
<li><p><code>start</code> is the time at which this sprite first appears.</p></li>
|
||||
<li><p><code>end</code> is the time at which it disappears.</p></li>
|
||||
<li><p><code>x</code> is the horizontal position at which it
|
||||
starts.</p></li>
|
||||
<li><p><code>x</code> is the horizontal position at which it starts.</p></li>
|
||||
<li><p><code>y</code> is the vertical position.</p></li>
|
||||
<li><p><code>dx</code> is the amount that the <code>x</code> position
|
||||
changes per frame.</p></li>
|
||||
<li><p><code>dy</code> is the amount that the <code>y</code> position
|
||||
changes per frame.</p></li>
|
||||
<li><p><code>dx</code> is the amount that the <code>x</code> position changes per frame.</p></li>
|
||||
<li><p><code>dy</code> is the amount that the <code>y</code> position changes per frame.</p></li>
|
||||
<li><p><code>cols</code> is the number of columns in each view.</p></li>
|
||||
<li><p><code>rows</code> is the number of rows in each view.</p></li>
|
||||
<li><p><code>viewcount</code> is the number of views to cycle
|
||||
through.</p></li>
|
||||
<li><p><code>viewcount</code> is the number of views to cycle through.</p></li>
|
||||
</ul>
|
||||
<p>Each such parameter line will be followed by <code>viewcount</code>
|
||||
view frames, each with <code>rows</code> rows and <code>cols</code>
|
||||
columns.</p>
|
||||
view frames, each with <code>rows</code> rows and <code>cols</code> columns.</p>
|
||||
<p>Input is terminated by end of file. Duh.</p>
|
||||
<p>Two samples input files are included; one a nice pastoral park scene,
|
||||
the other a bit of scrolling text.</p>
|
||||
<p>Two samples input files are included; one a nice pastoral park
|
||||
scene, the other a bit of scrolling text.</p>
|
||||
<h3 id="running-the-animation">RUNNING THE ANIMATION</h3>
|
||||
<p>Try one of these methods to get the animation to run:</p>
|
||||
<ol type="1">
|
||||
@@ -233,70 +225,48 @@ the other a bit of scrolling text.</p>
|
||||
<li>Redirect the output to a file, like this:</li>
|
||||
</ol>
|
||||
<div class="sourceCode" id="cb7"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./schnitzi</span> <span class="op"><</span> input.dat <span class="op">></span> output.dat</span></code></pre></div>
|
||||
<p>Then, open the output file, select the text, and copy it to your
|
||||
system pasteboard/cut/selection buffer and paste it into vi. The paste
|
||||
is NOT the vi paste command, but rather an action you take within your
|
||||
operating system. On a Windows machine running vi via Cygwin,
|
||||
“Edit|Paste” is a right-click menu option on the top window bar.</p>
|
||||
<p>Then, open the output file, select the text, and copy it
|
||||
to your system pasteboard/cut/selection buffer and paste
|
||||
it into vi. The paste is NOT the vi paste command, but
|
||||
rather an action you take within your operating system.
|
||||
On a Windows machine running vi via Cygwin, “Edit|Paste”
|
||||
is a right-click menu option on the top window bar.</p>
|
||||
<ol start="3" type="1">
|
||||
<li>Memorize the output, and type it into vi really really fast.</li>
|
||||
</ol>
|
||||
<h3 id="a-final-note">A FINAL NOTE</h3>
|
||||
<p>I would like to remind the Pixar Animation Studios that I retain
|
||||
royalties on this technique.</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-2004schnitzi"><a name="inventory"></a>Inventory
|
||||
for 2004/schnitzi</h1>
|
||||
<h1 id="inventory-for-2004schnitzi"><a name="inventory"></a>Inventory for 2004/schnitzi</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/2004/schnitzi/schnitzi.c">schnitzi.c</a>
|
||||
- entry source</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/Makefile">Makefile</a>
|
||||
- entry Makefile</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/schnitzi.orig.c">schnitzi.orig.c</a>
|
||||
- original source</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/schnitzi.inp0">schnitzi.inp0</a>
|
||||
- example input</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/schnitzi.inp1">schnitzi.inp1</a>
|
||||
- example input</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/try.sh">try.sh</a>
|
||||
- how to run</li>
|
||||
<li><a href="2004_schnitzi.tar.bz2">2004_schnitzi.tar.bz2</a> - download
|
||||
entry source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/schnitzi.c">schnitzi.c</a> - entry source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/Makefile">Makefile</a> - entry Makefile</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/schnitzi.orig.c">schnitzi.orig.c</a> - original source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/schnitzi.inp0">schnitzi.inp0</a> - example input</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/schnitzi.inp1">schnitzi.inp1</a> - example input</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/try.sh">try.sh</a> - how to run</li>
|
||||
<li><a href="2004_schnitzi.tar.bz2">2004_schnitzi.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/2004/schnitzi/.entry.json">.entry.json</a>
|
||||
- description of entry in JSON</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/.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/2004/schnitzi/.entry.json">.entry.json</a> - description of entry in JSON</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/.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/2004/schnitzi/README.md">README.md</a>
|
||||
- markdown source for index.html</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi/README.md">README.md</a> - markdown source for index.html</li>
|
||||
</ul>
|
||||
|
||||
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->
|
||||
|
||||
Reference in new issue
Block a user