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

2019/duble/index.html
+105 -162
View File
@@ -129,9 +129,9 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Etienne_Duble">Etienne
Duble</a><br> Location: <a href="../../location.html#FR">FR</a> -
<em>French Republic</em> (<em>France</em>) <br><br></li>
<li>Name: <a href="../../authors.html#Etienne_Duble">Etienne Duble</a><br>
Location: <a href="../../location.html#FR">FR</a> - <em>French Republic</em> (<em>France</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -141,14 +141,12 @@ Duble</a><br> Location: <a href="../../location.html#FR">FR</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></span></code></pre></div>
<p>There is an alternate version, the original, which does not work well
in macOS. See <a href="#alternate-code">Alternate code</a> below if you
are curious.</p>
<p>There is an alternate version, the original, which does not work well in macOS.
See <a href="#alternate-code">Alternate code</a> below if you are curious.</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#2019_duble">2019 duble bugs</a>.</p>
<p>For more detailed information see <a href="../../bugs.html#2019_duble">2019 duble 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">./prog</span> file</span></code></pre></div>
<h2 id="try">Try:</h2>
@@ -164,15 +162,12 @@ href="../../bugs.html#2019_duble">2019 duble bugs</a>.</p>
<hr />
<ul>
<li><strong>Arrow keys</strong>: move cursor.</li>
<li><code>p</code> key: enter <em>pen</em> mode (type <strong>p</strong>
again to return to the default <em>move</em> mode).</li>
<li><code>l</code> key: enter <em>line</em> mode (type
<strong>l</strong> again to validate the line and return to the
<em>move</em> mode).</li>
<li><code>c</code> key: cycle through a small set of different
<em>colors</em>.</li>
<li><code>q</code> key: quit the editor. The drawing is automatically
saved.</li>
<li><code>p</code> key: enter <em>pen</em> mode (type <strong>p</strong> again to return to the default <em>move</em>
mode).</li>
<li><code>l</code> key: enter <em>line</em> mode (type <strong>l</strong> again to validate the line and return
to the <em>move</em> mode).</li>
<li><code>c</code> key: cycle through a small set of different <em>colors</em>.</li>
<li><code>q</code> key: quit the editor. The drawing is automatically saved.</li>
</ul>
<p>The mode and current color is indicated at the bottom left corner of
the editor.</p>
@@ -180,202 +175,150 @@ the editor.</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">/tmp/drawing</span></span></code></pre></div>
<p>i.e. execute the file.</p>
<hr />
<p>WARNING: if the file is deleted it might lock any session still in
use. These will have to be killed from another shell session or by
closing the terminal tab (in other words don’t do this from the
console!). If the file cannot be opened in the beginning this will also
happen. This is discussed in <a href="../../bugs.html#2019_duble">2019
duble bugs</a>.</p>
<p>NOTE: this entry might leave sockets lying about in the current
working directory which you’ll have to delete manually. This is also
discussed in <a href="../../bugs.html#2019_duble">2019 duble
bugs</a>.</p>
<p>WARNING: if the file is deleted it might lock any session still in use. These
will have to be killed from another shell session or by closing the terminal tab
(in other words don’t do this from the console!). If the file cannot be opened
in the beginning this will also happen. This is discussed in
<a href="../../bugs.html#2019_duble">2019 duble bugs</a>.</p>
<p>NOTE: this entry might leave sockets lying about in the current working
directory which you’ll have to delete manually. This is also discussed in
<a href="../../bugs.html#2019_duble">2019 duble bugs</a>.</p>
<h2 id="alternate-code">Alternate code:</h2>
<p>An alternate version of this entry, <a
href="prog.alt.c">prog.alt.c</a>, is provided. This alternate code might
not work as well in macOS.</p>
<p>An alternate version of this entry, <a href="prog.alt.c">prog.alt.c</a>, is provided. This
alternate code might not work as well in macOS.</p>
<h3 id="alternate-build">Alternate build:</h3>
<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">make</span> alt</span></code></pre></div>
<h3 id="alternate-use">Alternate use:</h3>
<p>Use <code>prog.alt</code> as you would <code>prog</code> above.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>After starting the program, use the cursor keys, then try some modes,
like <code>p</code> or <code>l</code> (they toggle).</p>
<p>After starting the program, use the cursor keys, then try some modes, like <code>p</code>
or <code>l</code> (they toggle).</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="introduction">Introduction:</h3>
<p>This program is a <strong>graphics editor</strong>, running in the
terminal.</p>
<p>It provides <strong>collaborative</strong> features: one can join the
drawing session of someone else by just opening the same file!</p>
<p>This program is a <strong>graphics editor</strong>, running in the terminal.</p>
<p>It provides <strong>collaborative</strong> features: one can join the drawing session
of someone else by just opening the same file!</p>
<h3 id="getting-started">Getting started:</h3>
<p>The program can run on Linux, FreeBSD, macOS, and in most terminals.
See section <a href="#limits-portability">Limits, Portability</a> for
more info.</p>
<p>To build, type <code>make</code> (assuming gcc) or
<code>make CC=clang</code>.</p>
<p>Then you can start the program. It expects a file path as its first
argument:</p>
<div class="sourceCode" id="cb10"><pre
class="sourceCode sh"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./prog</span> /tmp/drawing</span></code></pre></div>
<p>(If not started this way, with a file, <code>prog</code> will refuse
to start.)</p>
See section <a href="#limits-portability">Limits, Portability</a> for more info.</p>
<p>To build, type <code>make</code> (assuming gcc) or <code>make CC=clang</code>.</p>
<p>Then you can start the program. It expects a file path as its first argument:</p>
<div class="sourceCode" id="cb10"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./prog</span> /tmp/drawing</span></code></pre></div>
<p>(If not started this way, with a file, <code>prog</code> will refuse to start.)</p>
<p>If the file does not exist, you will start with a blank drawing.</p>
<p>If someone else (or another <em>instance of yourself</em>, maybe?) is
already editing this file, you will join the session!</p>
<p>If someone else (or another <em>instance of yourself</em>, maybe?) is already
editing this file, you will join the session!</p>
<h3 id="edit-features">Edit features:</h3>
<ul>
<li><strong>arrow keys</strong>: move cursor.</li>
<li><code>p</code> key: enter <em>pen</em> mode (type <strong>p</strong>
again to return to the default <em>move</em> mode).</li>
<li><code>l</code> key: enter <em>line</em> mode (type
<strong>l</strong> again to validate the line and return to the
<em>move</em> mode).</li>
<li><code>c</code> key: cycle through a small set of different
<em>colors</em>.</li>
<li><code>q</code> key: quit the editor. The drawing is automatically
saved.</li>
<li><code>p</code> key: enter <em>pen</em> mode (type <strong>p</strong> again to return to the default <em>move</em> mode).</li>
<li><code>l</code> key: enter <em>line</em> mode (type <strong>l</strong> again to validate the line and return to the <em>move</em> mode).</li>
<li><code>c</code> key: cycle through a small set of different <em>colors</em>.</li>
<li><code>q</code> key: quit the editor. The drawing is automatically saved.</li>
</ul>
<p>The mode and current color is indicated at the bottom left corner of
the editor.</p>
<h3 id="bonus-features">Bonus features:</h3>
<ul>
<li>If you just want to display the content of a drawing file, you do
not need to start the editor. Just <strong>execute the drawing
file</strong>: <code>./&lt;the-file&gt;</code>. (This will fail if
someone is still editing the file, though.)</li>
<li><code>ls --color &lt;drawing-files...&gt;</code> will probably
select different colors to indicate whether a drawing file is being
edited or not. :-)</li>
<li>If you just want to display the content of a drawing file, you do not
need to start the editor. Just <strong>execute the drawing file</strong>: <code>./&lt;the-file&gt;</code>.
(This will fail if someone is still editing the file, though.)</li>
<li><code>ls --color &lt;drawing-files...&gt;</code> will probably select different colors
to indicate whether a drawing file is being edited or not. :-)</li>
</ul>
<h3 id="obfuscation">Obfuscation:</h3>
<p>You will probably have a hard time analyzing this entry, because:</p>
<ul>
<li>Analyzing a system made of several communicating programs is known
to be a complex task. (And if you think that observing a single-user
drawing session will be a good starting point, read on.)</li>
<li>Code coverage of single vs multi-user sessions is more or less the
same. :-)</li>
<li>Code coverage when using <em>move</em>, <em>pen</em> or
<em>line</em> modes is almost the same. (so, is there a Bresenham
algorithm somewhere??)</li>
<li>Some OS resource values and <code>stdlib.h</code> call results are
inferred.</li>
<li>Analyzing a system made of several communicating programs is known to
be a complex task. (And if you think that observing a single-user drawing
session will be a good starting point, read on.)</li>
<li>Code coverage of single vs multi-user sessions is more or less the same. :-)</li>
<li>Code coverage when using <em>move</em>, <em>pen</em> or <em>line</em> modes is almost the same.
(so, is there a Bresenham algorithm somewhere??)</li>
<li>Some OS resource values and <code>stdlib.h</code> call results are inferred.</li>
<li>Whenever possible, variable names are reused.</li>
<li>You might start analyzing escape code sequences right now, but
warming up your brain is actually recommended. Start with a simple
question such as: <em>in inverse video mode, will a space char show the
foreground color or background color?</em></li>
<li>You might start analyzing escape code sequences right now, but warming up
your brain is actually recommended. Start with a simple question such as:
<em>in inverse video mode, will a space char show the foreground color or
background color?</em></li>
</ul>
<h3 id="a-few-more-things">A few more things:</h3>
<p>Did you notice the <code>enum</code> declaration? Could it be just an
<code>int</code> or <code>const int</code> variable, instead? (spoiler:
<a href="http://c-faq.com/ansi/constasconst.html"
class="uri">http://c-faq.com/ansi/constasconst.html</a>)</p>
<p>If your keyboard has no arrow keys, you can probably find alternate
keys by reading the source code.</p>
<p>Did you notice the <code>enum</code> declaration? Could it be just an <code>int</code> or <code>const int</code>
variable, instead? (spoiler: <a href="http://c-faq.com/ansi/constasconst.html" class="uri">http://c-faq.com/ansi/constasconst.html</a>)</p>
<p>If your keyboard has no arrow keys, you can probably find alternate keys by
reading the source code.</p>
<h3 id="limits-portability">Limits, Portability:</h3>
<p>I tested the program on several Linux systems, on FreeBSD 12, and on
macOS (Mojave).</p>
<p>On Linux, the program uses an OS-specific detail to hide
communication artefacts, and avoids the need to remove them on exit.
<p>On Linux, the program uses an OS-specific detail to hide communication
artefacts, and avoids the need to remove them on exit.
Since this is Linux-specific, it was not possible on FreeBSD or macOS.
Its behavior is a little more <em>dirty</em> there.</p>
<p>The program should work on most terminals that support 8-bit colors,
inverse video mode, and movement escape codes, e.g. <code>xterm</code>,
<code>gnome-terminal</code>, <code>terminator</code>, etc.</p>
<p>Note: the drawing files <code>prog</code> generates are probably even
more portable than <code>prog</code> itself!</p>
inverse video mode, and movement escape codes, e.g. <code>xterm</code>, <code>gnome-terminal</code>,
<code>terminator</code>, etc.</p>
<p>Note: the drawing files <code>prog</code> generates are probably even more portable than
<code>prog</code> itself!</p>
<h3 id="drawing-area-size">Drawing area size:</h3>
<h4 id="the-drawing-area-size-is-set-at-compilation-time">The drawing
area size is set at compilation time:</h4>
<p>The default size is the one of my xterm (see top of Makefile). You
may set it to the full size of your terminal window by typing:</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">make</span> clobber fullscreen</span></code></pre></div>
<h4 id="the-drawing-area-size-is-set-at-compilation-time">The drawing area size is set at compilation time:</h4>
<p>The default size is the one of my xterm (see top of Makefile).
You may set it to the full size of your terminal window by typing:</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">make</span> clobber fullscreen</span></code></pre></div>
<p>IMPORTANT NOTES:</p>
<ul>
<li><strong>The program compiled with a given size will fail to reload a
drawing file with a different size!</strong></li>
<li>No scrolling is implemented (sorry but that would be too much for
rule2!), so any peer reaching the session should have a terminal with
the same size or larger.</li>
<li><strong>The program compiled with a given size will fail to reload a drawing file
with a different size!</strong></li>
<li>No scrolling is implemented (sorry but that would be too much for rule2!),
so any peer reaching the session should have a terminal with the same
size or larger.</li>
</ul>
<h3 id="prog.c-vs-prog.alt.c"><a href="prog.c">prog.c</a> vs <a
href="prog.alt.c">prog.alt.c</a></h3>
<p>The file <a href="prog.alt.c">prog.alt.c</a> is the one I
submitted.</p>
<p>The judges proposed a small update: the program was using macro
<code>FD_SET</code> inside an expression, which breaks compilation on
macOS. Wrapping this macro into a function was enough to fix this
compilation issue.</p>
<p>However, that was not enough to make the program work on macOS. If
you analyse the program you will see that it heavily relies on OS
resources. And, for this first version of the program, you even needed
to increase default <code>sysctl</code> parameters to make it work on
FreeBSD (this was the purpose of file <a
href="check-os.sh">check-os.sh</a>). I tried hard to tune macOS the
same, but failed.</p>
<p>The simple fact the Judges proposed this update meant they wish it
could work on Mac. And if the judges wish something, it <strong>has
to</strong> be done. ;) So I refactored a little more the program to
reduce OS resources consumption. Or maybe not reduce consumption, but
consume them differently… And I obtained <a href="prog.c">prog.c</a>.
With this version, no need to touch <code>sysctl</code> parameters, and
it works on macOS too! I must confess it was challenging to remain below
the size limit with this little change.</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>
<h3 id="prog.c-vs-prog.alt.c"><a href="prog.c">prog.c</a> vs <a href="prog.alt.c">prog.alt.c</a></h3>
<p>The file <a href="prog.alt.c">prog.alt.c</a> is the one I submitted.</p>
<p>The judges proposed a small update: the program was using macro <code>FD_SET</code> inside an
expression, which breaks compilation on macOS. Wrapping this macro into a
function was enough to fix this compilation issue.</p>
<p>However, that was not enough to make the program work on macOS. If you analyse
the program you will see that it heavily relies on OS resources. And, for this
first version of the program, you even needed to increase default <code>sysctl</code>
parameters to make it work on FreeBSD (this was the purpose of file
<a href="check-os.sh">check-os.sh</a>). I tried hard to tune macOS the same, but failed.</p>
<p>The simple fact the Judges proposed this update meant they wish it could work on
Mac. And if the judges wish something, it <strong>has to</strong> be done. ;) So I
refactored a little more the program to reduce OS resources consumption. Or
maybe not reduce consumption, but consume them differently… And I obtained
<a href="prog.c">prog.c</a>. With this version, no need to touch <code>sysctl</code> parameters, and
it works on macOS too! I must confess it was challenging to remain below the
size limit with this little change.</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-2019duble"><a name="inventory"></a>Inventory for
2019/duble</h1>
<h1 id="inventory-for-2019duble"><a name="inventory"></a>Inventory for 2019/duble</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/2019/duble/prog.c">prog.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/prog.alt.c">prog.alt.c</a>
- alternative source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/prog.orig.c">prog.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/check-os.sh">check-os.sh</a>
- check the operating system for compatibility</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/fullscreen.sh">fullscreen.sh</a>
- determine full screen size for make fullscreen</li>
<li><a href="2019_duble.tar.bz2">2019_duble.tar.bz2</a> - download entry
source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/prog.c">prog.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/prog.alt.c">prog.alt.c</a> - alternative source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/prog.orig.c">prog.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/check-os.sh">check-os.sh</a> - check the operating system for compatibility</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/fullscreen.sh">fullscreen.sh</a> - determine full screen size for make fullscreen</li>
<li><a href="2019_duble.tar.bz2">2019_duble.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/2019/duble/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/.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/2019/duble/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/.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/2019/duble/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->