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
@@ -122,16 +122,15 @@
|
||||
|
||||
<p>The following are a few screen dumps of:</p>
|
||||
<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="va">SIZE</span><span class="op">=</span>100 <span class="va">SHEDS</span><span class="op">=</span>5 <span class="va">GROW</span><span class="op">=</span>-10 <span class="va">SHED</span><span class="op">=</span>50 <span class="va">MAXSIZE</span><span class="op">=</span>250 <span class="ex">./prog</span></span></code></pre></div>
|
||||
<p>As you will see it took 17 bugs to get down to below 0. Notice how I
|
||||
had to get down to 0 more than once: because I moved enough times before
|
||||
I got the last bug that I grew by 5 in size. I then however moved a bit
|
||||
more and ate a bug which brought me down to -5 therefore winning at the
|
||||
max size of 250. This then showed:</p>
|
||||
<p>As you will see it took 17 bugs to get down to below 0. Notice how I had to get
|
||||
down to 0 more than once: because I moved enough times before I got the last
|
||||
bug that I grew by 5 in size. I then however moved a bit more and ate a bug
|
||||
which brought me down to -5 therefore winning at the max size of 250. This then
|
||||
showed:</p>
|
||||
<pre><code>YOU WIN!
|
||||
X:62/89 Y:5/25 S:250/250 B:17</code></pre>
|
||||
<p>Observe all the arrows on the screen; that’s where a bug was that I
|
||||
ate and then I split off losing 10 in size. The first dump I’m already
|
||||
at 15/250:</p>
|
||||
<p>Observe all the arrows on the screen; that’s where a bug was that I ate and
|
||||
then I split off losing 10 in size. The first dump I’m already at 15/250:</p>
|
||||
<pre><code>X:17/89 Y:15/25 S:15/250 B:13
|
||||
##########################################################################################
|
||||
# <ooooooooo o <ooooooooo* #
|
||||
@@ -158,8 +157,7 @@ at 15/250:</p>
|
||||
# o o> #
|
||||
# oooooo #
|
||||
##########################################################################################</code></pre>
|
||||
<p>But here now I’m at 0; the head is marked <code>H</code> and it’s
|
||||
moving left.</p>
|
||||
<p>But here now I’m at 0; the head is marked <code>H</code> and it’s moving left.</p>
|
||||
<pre><code>X:19/89 Y:12/25 S:0/250 B:16
|
||||
##########################################################################################
|
||||
# <ooooooooo o <oooooooo <ooooooo #
|
||||
@@ -187,10 +185,9 @@ moving left.</p>
|
||||
# oooooo #
|
||||
##########################################################################################</code></pre>
|
||||
<p>I ended up moving enough times where my size went back up to 5.</p>
|
||||
<p>Below the snake is moving right and its head is indicated by a
|
||||
<code>H</code> with the line marked at the right; the bug is marked as
|
||||
<code>B</code> and is also marked at the right. Notice how it’s in the
|
||||
body of the snake (but see below)!</p>
|
||||
<p>Below the snake is moving right and its head is indicated by a <code>H</code> with the line
|
||||
marked at the right; the bug is marked as <code>B</code> and is also marked at the right.
|
||||
Notice how it’s in the body of the snake (but see below)!</p>
|
||||
<pre><code>X:55/89 Y:4/25 S:5/250 B:16
|
||||
##########################################################################################
|
||||
# <ooooooooo o <oooooooo <ooooooo #
|
||||
@@ -217,11 +214,10 @@ body of the snake (but see below)!</p>
|
||||
# o o> #
|
||||
# oooooo #
|
||||
##########################################################################################</code></pre>
|
||||
<p>But did you see anything strange? The bug is on the fourth line below
|
||||
the upper wall. However it appears to be inside the body of the snake!
|
||||
But actually that’s just where the snake split off at some point: the
|
||||
snake no longer occupies that place and indeed I could safely go through
|
||||
that part of the screen.</p>
|
||||
<p>But did you see anything strange? The bug is on the fourth line below the upper wall.
|
||||
However it appears to be inside the body of the snake! But actually that’s just where
|
||||
the snake split off at some point: the snake no longer occupies that place and indeed I
|
||||
could safely go through that part of the screen.</p>
|
||||
|
||||
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
|
||||
<!-- START: this line starts content from: inc/after-content.default.html -->
|
||||
|
||||
Reference in new issue
Block a user