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
+47
-77
@@ -129,9 +129,9 @@
|
||||
|
||||
<h2 id="author"><a name="author"></a>Author:</h2>
|
||||
<ul>
|
||||
<li>Name: <a href="../../authors.html#Jens_Schweikhardt">Jens
|
||||
Schweikhardt</a><br> Location: <a href="../../location.html#DE">DE</a> -
|
||||
<em>Federal Republic of Germany</em> (<em>Germany</em>) <br><br></li>
|
||||
<li>Name: <a href="../../authors.html#Jens_Schweikhardt">Jens Schweikhardt</a><br>
|
||||
Location: <a href="../../location.html#DE">DE</a> - <em>Federal Republic of Germany</em> (<em>Germany</em>)
|
||||
<br><br></li>
|
||||
</ul>
|
||||
|
||||
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
|
||||
@@ -144,36 +144,31 @@ Schweikhardt</a><br> Location: <a href="../../location.html#DE">DE</a> -
|
||||
<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#2001_schweikh">2001 schweikh bugs</a>.</p>
|
||||
<p>For more detailed information see <a href="../../bugs.html#2001_schweikh">2001 schweikh 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">./schweikh</span> string string2</span></code></pre></div>
|
||||
<p>This program will very likely crash or do something else if you do
|
||||
not give it two args.</p>
|
||||
<p>Note also that the glob pattern must match the whole string. See the
|
||||
author’s comments for details and a workaround.</p>
|
||||
<p>This program will very likely crash or do something else if you do not give it
|
||||
two args.</p>
|
||||
<p>Note also that the glob pattern must match the whole string. See the author’s
|
||||
comments for details and a workaround.</p>
|
||||
<p>There’s also no way to escape meta characters.</p>
|
||||
<p>This is supposed to happen. As is written in the <a
|
||||
href="http://catb.org/jargon/html/F/feature.html">The Jargon
|
||||
File</a>:</p>
|
||||
<p>This is supposed to happen. As is written in the
|
||||
<a href="http://catb.org/jargon/html/F/feature.html">The Jargon File</a>:</p>
|
||||
<pre><code>That's not a bug, that's a feature.</code></pre>
|
||||
<h2 id="try">Try:</h2>
|
||||
<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="ex">./try.sh</span></span></code></pre></div>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>Do you get the pattern here?</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<p>This one-liner program is a glob pattern matcher. It understands the
|
||||
glob characters <code>*</code> meaning ‘zero or more characters’ and
|
||||
<code>?</code> meaning exactly one character, just like your unix
|
||||
shell.</p>
|
||||
<p>Run it with two args, the string and the glob pattern. The exit
|
||||
status is 0 (shell true) when the pattern matches, 1 otherwise. The glob
|
||||
pattern must match the whole string, so you may want to use
|
||||
<code>*</code> at the beginning and end of the pattern if you are
|
||||
looking for something in the middle.</p>
|
||||
<p>You can use it for your shell scripting needs similar to a silent
|
||||
grep (and without <code>stdout</code> redirected to
|
||||
<code>/dev/null</code>):</p>
|
||||
<p>This one-liner program is a glob pattern matcher. It understands
|
||||
the glob characters <code>*</code> meaning ‘zero or more characters’ and
|
||||
<code>?</code> meaning exactly one character, just like your unix shell.</p>
|
||||
<p>Run it with two args, the string and the glob pattern. The exit status is 0
|
||||
(shell true) when the pattern matches, 1 otherwise. The glob pattern must match
|
||||
the whole string, so you may want to use <code>*</code> at the beginning and end of the
|
||||
pattern if you are looking for something in the middle.</p>
|
||||
<p>You can use it for your shell scripting needs similar to a silent grep
|
||||
(and without <code>stdout</code> redirected to <code>/dev/null</code>):</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="cf">if</span> <span class="ex">prog</span> <span class="st">"</span><span class="va">${VARIABLE}</span><span class="st">"</span> <span class="st">'<glob>'</span><span class="kw">;</span> <span class="cf">then</span></span>
|
||||
<span id="cb6-2"><a href="#cb6-2" aria-hidden="true" tabindex="-1"></a> <span class="bu">echo</span> VARIABLE matches</span>
|
||||
<span id="cb6-3"><a href="#cb6-3" aria-hidden="true" tabindex="-1"></a><span class="cf">else</span></span>
|
||||
@@ -182,83 +177,58 @@ grep (and without <code>stdout</code> redirected to
|
||||
<h3 id="bugs">Bugs</h3>
|
||||
<p>There is no way to escape the meta characters. Dammit Jim, I’m a
|
||||
one-liner, not a regexp lib.</p>
|
||||
<p>All obfuscation is obviously in the recursive <code>m()</code>
|
||||
function, an 86 character glob pattern evaluator, returning nonzero for
|
||||
a match:</p>
|
||||
<p>All obfuscation is obviously in the recursive <code>m()</code> function, an 86
|
||||
character glob pattern evaluator, returning nonzero for a match:</p>
|
||||
<ul>
|
||||
<li>Just a single complex return expression.</li>
|
||||
<li>Nested ternary operator <code>?:</code> to save on
|
||||
<code>if</code>/<code>else</code> verbosity.</li>
|
||||
<li>Short circuiting <code>&&</code> and <code>||</code> to save
|
||||
even more on <code>if</code>/<code>else</code> verbosity.</li>
|
||||
<li>Subtraction instead of an equality operator in
|
||||
<code>*t - 42</code>.</li>
|
||||
<li>Nested ternary operator <code>?:</code> to save on <code>if</code>/<code>else</code> verbosity.</li>
|
||||
<li>Short circuiting <code>&&</code> and <code>||</code> to save even more on <code>if</code>/<code>else</code> verbosity.</li>
|
||||
<li>Subtraction instead of an equality operator in <code>*t - 42</code>.</li>
|
||||
<li>ASCII codes for <code>*</code> and <code>?</code>.</li>
|
||||
<li>Careful use of blanks even though this year’s rules have extended
|
||||
that resource limit.</li>
|
||||
<li>The source is a complete preprocessed C program. Because it
|
||||
communicates with the world out there by means of <code>argv</code> and
|
||||
the exit status, there is no need for <code>stdio.h</code> bloat. An asm
|
||||
guru could surely squeeze this program in less than a screenful.</li>
|
||||
<li>The source is a complete preprocessed C program. Because it communicates
|
||||
with the world out there by means of <code>argv</code> and the exit status, there
|
||||
is no need for <code>stdio.h</code> bloat. An asm guru could surely squeeze this
|
||||
program in less than a screenful.</li>
|
||||
<li><code>indent(1)</code> is probably not too helpful.</li>
|
||||
</ul>
|
||||
<p>The recursion wonderfully and magically takes care of iteration and
|
||||
backtracking. I could tell you how it works but then I would have to
|
||||
<strike>kill</strike> request a NDA from you :-) Run it under a debugger
|
||||
with several inputs, it will be quite helpful and instructive. Handling
|
||||
of <code>?</code> is straightforward; for <code>*</code> start out with
|
||||
<code>*foo</code> and <code>foo*</code> against <code>foo</code>. How
|
||||
does it deal with sequences of adjacent <code>*</code>? How could this
|
||||
be improved? If all else fails, recode the <code>?:</code> operators
|
||||
with <code>if</code>/<code>else</code> and try again. For extra credit
|
||||
implement character classes like <code>[a-z]</code>.</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>
|
||||
<strike>kill</strike> request a NDA from you :-) Run it under a debugger with several
|
||||
inputs, it will be quite helpful and instructive. Handling of <code>?</code> is
|
||||
straightforward; for <code>*</code> start out with <code>*foo</code> and <code>foo*</code> against <code>foo</code>.
|
||||
How does it deal with sequences of adjacent <code>*</code>? How could this be
|
||||
improved? If all else fails, recode the <code>?:</code> operators with <code>if</code>/<code>else</code> and
|
||||
try again. For extra credit implement character classes like <code>[a-z]</code>.</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-2001schweikh"><a name="inventory"></a>Inventory
|
||||
for 2001/schweikh</h1>
|
||||
<h1 id="inventory-for-2001schweikh"><a name="inventory"></a>Inventory for 2001/schweikh</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/2001/schweikh/schweikh.c">schweikh.c</a>
|
||||
- entry source</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/Makefile">Makefile</a>
|
||||
- entry Makefile</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/schweikh.orig.c">schweikh.orig.c</a>
|
||||
- original source</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/try.sh">try.sh</a>
|
||||
- how to run</li>
|
||||
<li><a href="2001_schweikh.tar.bz2">2001_schweikh.tar.bz2</a> - download
|
||||
entry source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/schweikh.c">schweikh.c</a> - entry source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/Makefile">Makefile</a> - entry Makefile</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/schweikh.orig.c">schweikh.orig.c</a> - original source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/try.sh">try.sh</a> - how to run</li>
|
||||
<li><a href="2001_schweikh.tar.bz2">2001_schweikh.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/2001/schweikh/.entry.json">.entry.json</a>
|
||||
- description of entry in JSON</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/.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/2001/schweikh/.entry.json">.entry.json</a> - description of entry in JSON</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/.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/2001/schweikh/README.md">README.md</a>
|
||||
- markdown source for index.html</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/schweikh/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