fix more broken markdown links

Fixed stuff we broke by mistake, previously.

Ran `make www` to perform the above.

TODO: Fix stuff we broke by mistake doing the above.

TODO: Fix more broken markdown links.
This commit is contained in:
Landon Curt Noll committed 2024-04-26 16:25:17 -07:00
1 parent 4f95e3f3d6
commit 8bca099534
62 files changed
+181 -168

No files matched your search

+3 -3
View File
@@ -24,13 +24,13 @@ compiler.
## Remarks on some of the winning entries
This year's [Best of Show (carlini)](carlini/index.html) is such a novel way of
This year's [Best of Show - 2020/carlini](carlini/index.html) is such a novel way of
obfuscation that it would be worth of a special mention in the (future) Best of
IOCCC list!
For some reason, this year's set of winning entries contains three nostalgic games,
[Asteroids (tsoj)](tsoj/index.html), [Minesweeper (endoh1)](endoh1/index.html),
and [Snake (ferguson1)](ferguson1/index.html).
[Asteroids - 2020/tsoj](tsoj/index.html), [Minesweeper - 2020/endoh1](endoh1/index.html),
and [Snake - 2020/ferguson1](ferguson1/index.html).
An entry, [kurdyukov1](kurdyukov1/index.html), pays homage to previous entry
[2015/hou](2015/hou/index.html).
+1 -1
View File
@@ -742,7 +742,7 @@ snakeskin would be the same size the snake was and the snake would grow as it
slithered out. But that would fill the screen very quickly of course. Maybe the
snakeskin has some other purpose?</p>
<h2 id="snake-moves-faster-over-time">Snake moves faster over time</h2>
<p>In the game [Surround](https://en.wikipedia.org/wiki/Surround_(video_game) you
<p>In the game <a href="https://en.wikipedia.org/wiki/Surround_(video_game)">Surround</a> you
have no control over the speed. I believe there are five different speed levels
but the player has no control over it except the drawing mode. It would be
possible to make it so the snake moves faster over time. How often and by what
+1 -1
View File
@@ -505,7 +505,7 @@ snakeskin has some other purpose?
## Snake moves faster over time
In the game [Surround](https://en.wikipedia.org/wiki/Surround_(video_game) you
In the game [Surround](https://en.wikipedia.org/wiki/Surround_&#x28;video_game&#x29;) you
have no control over the speed. I believe there are five different speed levels
but the player has no control over it except the drawing mode. It would be
possible to make it so the snake moves faster over time. How often and by what
+1 -1
View File
@@ -233,7 +233,7 @@ very important.
<div id="toc">
* ['Bugs'](#bugs)
* [NAQs/IAQs (Never/Infrequently Asked Questions)](#naqs)
* [NAQs/IAQs - Never/Infrequently Asked Questions](#naqs)
- [Do I have any inspirations for this entry?](#inspirations)
- [Are there any features I thought of that I wanted to implement but did not get to for some reason or another?](#features)
- [Are there ways that one can make this game easier?](#easier)
+1 -1
View File
@@ -5,7 +5,7 @@
<div id="toc">
* [Built-in test unit for some features!](#builtin-test-unit)
* [The snake doesn't seem to be moving](#stillsnake)
* [getch() also accepts input from some input hardware other than keyboards](#getch)
* [getch&#x28;&#x29; also accepts input from some input hardware other than keyboards](#getch)
* [SIZE=0 is the same as SIZE=1 and other oddities](#size)
* ['I was a few places behind my tail and I ran into it!'](#bitetail)
* [With negative growth the snake drops from the middle of the body](#middleofsnake)
+3 -3
View File
@@ -401,12 +401,12 @@ for the input keys.</p>
<ul>
<li><a href="#warning"><strong>Photosensitive epilepsy/Stimulation overload trigger warnings</strong></a></li>
<li><a href="#drawing">Drawing / Practice mode</a></li>
<li><a href="#auto">Computer playing / Automatic mode (<strong>Photosensitive epilepsy/Stimulation overload trigger</strong>)</a>
<li><a href="#auto">Computer playing / Automatic mode (Photosensitive epilepsy/Stimulation overload trigger)</a>
<ul>
<li><a href="#auto-variations">Variations</a></li>
</ul></li>
<li><a href="#grow-shrink">Grow-Shrink (Positive/Negative Winning) mode</a></li>
<li><a href="#hypnotic">Hypnotic / Sleepy mode (<strong>Photosensitive epilepsy/Stimulation overload trigger</strong>)</a></li>
<li><a href="#hypnotic">Hypnotic / Sleepy mode (Photosensitive epilepsy/Stimulation overload trigger)</a></li>
<li><a href="#stim">Stimulation / Calming mode</a></li>
<li><a href="#other-ideas">Other ideas</a></li>
</ul></li>
@@ -901,7 +901,7 @@ also has this mode:</p>
of them (the above is option 5; others are 4, 15 and 16 but only options 4 and 5
are called Grow / Shrink).</p>
<div id="hypnotic">
<h2 id="hypnotic-sleepy-mode-photosensitive-epilepsystimulation-overload-trigger"><a href="#toc">Hypnotic / Sleepy mode (<strong>Photosensitive epilepsy/Stimulation overload trigger</strong>)</a></h2>
<h2 id="hypnotic-sleepy-mode-photosensitive-epilepsystimulation-overload-trigger"><a href="#toc">Hypnotic / Sleepy mode (Photosensitive epilepsy/Stimulation overload trigger)</a></h2>
</div>
<p><strong>Photosensitive epilepsy/stimulation overload trigger warning:</strong>
For those who have epilepsy or are susceptible to stimulation overload from
+7 -7
View File
@@ -14,7 +14,7 @@ for the input keys.
* [Playing the game](#playing)
* [Walls](#walls)
* [Cannibalism](#cannibalism)
* [Stretching (shedding)](#shedding)
* [Stretching &#x28;shedding&#x29;](#shedding)
* [Winning](#winning)
* [Quitting](#quitting)
@@ -23,10 +23,10 @@ for the input keys.
* [**Photosensitive epilepsy/Stimulation overload trigger warnings**](#warning)
* [Drawing / Practice mode](#drawing)
* [Computer playing / Automatic mode (**Photosensitive epilepsy/Stimulation overload trigger**)](#auto)
* [Computer playing / Automatic mode &#x28;Photosensitive epilepsy/Stimulation overload trigger&#x29;](#auto)
* [Variations](#auto-variations)
* [Grow-Shrink (Positive/Negative Winning) mode](#grow-shrink)
* [Hypnotic / Sleepy mode (**Photosensitive epilepsy/Stimulation overload trigger**)](#hypnotic)
* [Grow-Shrink &#x28;Positive/Negative Winning&#x29; mode](#grow-shrink)
* [Hypnotic / Sleepy mode &#x28;Photosensitive epilepsy/Stimulation overload trigger&#x29;](#hypnotic)
* [Stimulation / Calming mode](#stim)
* [Other ideas](#other-ideas)
@@ -44,7 +44,7 @@ for the input keys.
* [GROW / SHEDS - Growth / Shedding sizes](#growth)
7. [Conclusion (and inspirational words for everyone)](#conclusions)
7. [Conclusion &#x28;and inspirational words for everyone&#x29;](#conclusions)
</div>
@@ -728,7 +728,7 @@ are called Grow / Shrink).
<div id="hypnotic">
## <a href="#toc">Hypnotic / Sleepy mode (**Photosensitive epilepsy/Stimulation overload trigger**)</a>
## <a href="#toc">Hypnotic / Sleepy mode &#x28;Photosensitive epilepsy/Stimulation overload trigger&#x29;</a>
</div>
**Photosensitive epilepsy/stimulation overload trigger warning:**
@@ -892,7 +892,7 @@ it will take the number of movements before it is 'its full size'.
<div id="conclusions">
# 7. <a href="#toc">Conclusion (and inspirational words for everyone)</a>
# 7. <a href="#toc">Conclusion &#x28;and inspirational words for everyone&#x29;</a>
</div>
I believe that this file has given more than enough information for anyone to
+1 -1
View File
@@ -578,7 +578,7 @@ very important.</p>
<div id="toc">
<ul>
<li><a href="#bugs">‘Bugs’</a></li>
<li><a href="#naqs">NAQs/IAQs (Never/Infrequently Asked Questions)</a>
<li><a href="#naqs">NAQs/IAQs - Never/Infrequently Asked Questions</a>
<ul>
<li><a href="#inspirations">Do I have any inspirations for this entry?</a></li>
<li><a href="#features">Are there any features I thought of that I wanted to implement but did not get to for some reason or another?</a></li>
+1 -1
View File
@@ -401,7 +401,7 @@ already knew that so no harm there, hey?</p>
<li><a href="#resizing">Collision detection when resizing the window of the game</a></li>
</ul></li>
<li><a href="#obfuscation">Obfuscation</a></li>
<li><a href="#skinning">Skinning the snake (i.e. decreasing the iocccsize)</a></li>
<li><a href="#skinning">Skinning the snake (i.e., decreasing the iocccsize)</a></li>
<li><a href="#size">A few more interesting size optimisations</a></li>
</ul>
</div>
+2 -2
View File
@@ -15,12 +15,12 @@ already knew that so no harm there, hey?
<div id="toc">
- [How does it work?](#works)
- [How does the snake movement work?](#movement)
- [Drawing (manual) and computer playing (automatic) modes](#manual-automatic)
- [Drawing &#x28;manual&#x29; and computer playing &#x28;automatic&#x29; modes](#manual-automatic)
- [Collision detection](#collision)
* [Cannibal collision detection](#cannibalcollision)
* [Collision detection when resizing the window of the game](#resizing)
- [Obfuscation](#obfuscation)
- [Skinning the snake (i.e. decreasing the iocccsize)](#skinning)
- [Skinning the snake &#x28;i.e., decreasing the iocccsize&#x29;](#skinning)
- [A few more interesting size optimisations](#size)
</div>
+1 -1
View File
@@ -379,7 +379,7 @@
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- BEFORE: 1st line of markdown file: 2020/ferguson1/troubleshooting.md -->
<h1 id="troubleshooting-snake">Troubleshooting Snake</h1>
<p>9 Troubleshooting Snake</p>
<p>In this file I have a list of a number of possible problems that could show up
under some situations as well as some things that might appear to be happening
or be a problem but actually are not. For each one I have included a summary, a
+4 -4
View File
@@ -1,4 +1,4 @@
# Troubleshooting Snake
9 Troubleshooting Snake
In this file I have a list of a number of possible problems that could show up
under some situations as well as some things that might appear to be happening
@@ -8,15 +8,15 @@ anything that can cause more than one issue I will list those separately to keep
it as structured as possible/easiest to find.
<div id="top">
* [The top wall isn't (all/some of the time) visible!](#topwall)
* [The top wall isn't &#x28;all/some of the time&#x29; visible!](#topwall)
* [The snake isn't moving!](#notmoving)
* [I can't see the snake head (or other part of the snake)!](#invisiblehead)
* [I can't see the snake head &#x28;or other part of the snake&#x29;!](#invisiblehead)
* [I can't see the bug!](#invisiblebug)
* [The game froze!](#froze)
* [The game gets slower as the snake gets bigger!](#bigsnake)
* [I set SIZE=0 GROW=1, ate a bug but still only the head was visible! Why?](#headonly)
* [I like black text on a white background but even with a white background terminal it ends up black!](#monochrome)
* [The text is hard to see (not bright enough)!](#toodark)
* [The text is hard to see &#x28;not bright enough&#x29;!](#toodark)
* [Can I move the snake faster temporarily without having to modify the wait time?](#movefaster)
* [On environmental variables more generally and string to int conversions](#envvars)
* [Errors and error reporting](#errors)
+3 -3
View File
@@ -452,9 +452,9 @@ For examples using it (and a delicious challenge) see [recode.html][] (or
### A parser subtlety that could cause confusion
</div>
The parser is in a sense rather rudimentary but allows for both interactive and
automatic (e.g. via the [recode]((%%REPO_URL%%/2020/ferguson2/recode.c) program) input. This does mean that
something like the following can happen:
The parser is in a sense rather rudimentary but allows for both interactive and automatic
(e.g., via the [recode](%%REPO_URL%%/2020/ferguson2/recode.c) program) input.
This does mean that something like the following can happen:
``` <!---sh-->
$ ./prog -
+3 -3
View File
@@ -707,9 +707,9 @@ make it more flexible by a wrapper program.</p>
<div id="parsersubtlety">
<h3 id="a-parser-subtlety-that-could-cause-confusion">A parser subtlety that could cause confusion</h3>
</div>
<p>The parser is in a sense rather rudimentary but allows for both interactive and
automatic (e.g. via the <a href="(https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/recode.c)%20program">recode</a> input. This does mean that
something like the following can happen:</p>
<p>The parser is in a sense rather rudimentary but allows for both interactive and automatic
(e.g., via the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/recode.c">recode</a> program) input.
This does mean that something like the following can happen:</p>
<pre><code> $ ./prog -
Ring 1: 1AB
Setting 1: Position 1: Ring 2: 2CD
+3 -3
View File
@@ -458,8 +458,8 @@ if you don’t give the option to read in a file for input.</p>
Plugboard pair #09: RU
Plugboard pair #10: VG
1WX5AK4RE1XEHJSAPYCIZBWDQNRUVGIOCCC</code></pre>
<p>Though you won’t find some of those strings in [recode.c]((https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/recode.c) or
[prog.c]((https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/prog.c). Yes the <code>WAR</code> for the Ringstellung (Ring settings) is an
<p>Though you won’t find some of those strings in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/recode.c">recode.c</a> or
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/prog.c">prog.c</a>. Yes the <code>WAR</code> for the Ringstellung (Ring settings) is an
amusing coincidence <em>but it really did happen!</em></p>
<p>As for <code>-f</code> the contents would be output with the settings e.g. to pipe to
<code>prog</code> itself (as if you redirected the file contents to the Enigma machine for
@@ -585,7 +585,7 @@ pair</a>; this can be done in
a number of ways but two dots is one. Notice also that it’s in a different order
than the simulator: because with the size restrictions on my entry I saved bytes
by using the same loop where I could. It just felt more natural to have them
grouped together in a configurator for the [simulator]((https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/prog.c).</p>
grouped together in a configurator for the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/prog.c">simulator</a>.</p>
<pre><code> $ echo 1AA2AA3AA2ABCD..EFGHIJKLMNOPQRIOCCC | ./prog - 2&gt;/dev/null
HQNVO
$ echo 1AA2AA3AA2ABCD..EFGHIJKLMNOPQRIOCCC | ./prog - 2&gt;/dev/null | echo 1AA2AA3AA2ABCD..EFGHIJKLMNOPQRHQNVO | ./prog - 2&gt;/dev/null
+4 -4
View File
@@ -18,7 +18,7 @@ have to if you don't wish to.
- [Only write config file](#onlyconfig)
- [Reusing a configuration](#reuseconfig)
- [Write config file, read data file and pass to Enigma simulator](#passtoenigma)
- [Piping directly to the Enigma code once (with randomised settings, saved)](#directlytoenigma)
- [Piping directly to the Enigma code once &#x28;with randomised settings, saved&#x29;](#directlytoenigma)
- [Usage conclusion](#conclusion)
- [Example additions](#additions)
- [Example uses](#exampleuses)
@@ -97,8 +97,8 @@ if you don't give the option to read in a file for input.
1WX5AK4RE1XEHJSAPYCIZBWDQNRUVGIOCCC
```
Though you won't find some of those strings in [recode.c]((%%REPO_URL%%/2020/ferguson2/recode.c) or
[prog.c]((%%REPO_URL%%/2020/ferguson2/prog.c). Yes the `WAR` for the Ringstellung (Ring settings) is an
Though you won't find some of those strings in [recode.c](%%REPO_URL%%/2020/ferguson2/recode.c) or
[prog.c](%%REPO_URL%%/2020/ferguson2/prog.c). Yes the `WAR` for the Ringstellung (Ring settings) is an
amusing coincidence *but it really did happen!*
As for `-f` the contents would be output with the settings e.g. to pipe to
@@ -265,7 +265,7 @@ pair](https://www.cryptomuseum.com/crypto/enigma/i/sb.htm); this can be done in
a number of ways but two dots is one. Notice also that it's in a different order
than the simulator: because with the size restrictions on my entry I saved bytes
by using the same loop where I could. It just felt more natural to have them
grouped together in a configurator for the [simulator]((%%REPO_URL%%/2020/ferguson2/prog.c).
grouped together in a configurator for the [simulator](%%REPO_URL%%/2020/ferguson2/prog.c).
``` <!---sh-->
$ echo 1AA2AA3AA2ABCD..EFGHIJKLMNOPQRIOCCC | ./prog - 2>/dev/null
+3 -3
View File
@@ -398,12 +398,12 @@ system may require certain changes (add or remove a library, add or remove a
lacking, you may need to compile using clang or gcc instead of your local
compiler.</p>
<h2 id="remarks-on-some-of-the-winning-entries">Remarks on some of the winning entries</h2>
<p>This year’s <a href="carlini/index.html">Best of Show (carlini)</a> is such a novel way of
<p>This year’s <a href="carlini/index.html">Best of Show - 2020/carlini</a> is such a novel way of
obfuscation that it would be worth of a special mention in the (future) Best of
IOCCC list!</p>
<p>For some reason, this year’s set of winning entries contains three nostalgic games,
<a href="tsoj/index.html">Asteroids (tsoj)</a>, <a href="endoh1/index.html">Minesweeper (endoh1)</a>,
and <a href="ferguson1/index.html">Snake (ferguson1)</a>.</p>
<a href="tsoj/index.html">Asteroids - 2020/tsoj</a>, <a href="endoh1/index.html">Minesweeper - 2020/endoh1</a>,
and <a href="ferguson1/index.html">Snake - 2020/ferguson1</a>.</p>
<p>An entry, <a href="kurdyukov1/index.html">kurdyukov1</a>, pays homage to previous entry
<a href="2015/hou/index.html">2015/hou</a>.</p>
<p>…We’ll stop spouting spoilers now. Have fun exploring all the entries!</p>
+1 -1
View File
@@ -66,7 +66,7 @@ the Elves in Tolkien's Legendarium. It means sound taste (plural is lámatyáver
and it refers to phonaesthesia - in other words, it refers to the pleasure of
sound and form of words. It's discussed in [Morgoth's
Ring](https://en.wikipedia.org/wiki/Morgoth%27s_Ring), volume X of [History of
Middle-earth (HoMe)](https://en.wikipedia.org/wiki/The_History_of_Middle-earth).
Middle-earth &#x28;HoMe&#x29;](https://en.wikipedia.org/wiki/The_History_of_Middle-earth).
Now can you appreciate the award title a bit better?