mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename *.text *.md

Browse Source 
As luck would have it the only entries where this applied were my own.
The links/references to these files have been changed in the files.

An unfortunate problem is that in 2020/ferguson1 there are several
*.markdown files. I will have to go through these and figure out which
ones should be changed to .md and which ones can be removed. This can
happen later but in the meantime the references are to .md. I believe
the only difference is that the .md has the footer added by the judges.
This was a workaround with the fact that I wasn't sure (and still am not
entirely sure) the generation of the html files will work. It might be
that the .markdown files have the footer and the .md files do not but
this can be dealt with later anyway.
This commit is contained in:
Cody Boone Ferguson committed 2023-02-08 06:21:11 -08:00
1 parent d844165510
commit 19d5c3a848
27 files changed
+120 -102
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2020/ferguson1/.gitignore
+6
View File
@@ -0,0 +1,6 @@
play
prog.alt
snake
snake-colours
snake.alt
termcaps
2020/ferguson1/COMPILING
+3 -3
View File
@@ -4,9 +4,9 @@ will need two different packages: the library itself but also the dev package
that has the header files etc. If you use the Makefile obviously you need `make'
too.
In gameplay.markdown I show how to easily customise the colours, set up
different gameplay modes and various other things. The troubleshooting.markdown
and terminals.markdown as well as bugs.markdown include a variety of information
In gameplay.md I show how to easily customise the colours, set up
different gameplay modes and various other things. The troubleshooting.md
and terminals.md as well as bugs.md include a variety of information
should you run into trouble.
--
2020/ferguson1/Makefile
+4 -4
View File
@@ -421,10 +421,10 @@ MAY_NEED_GCC= gcc
##############################
#
OBJ= prog.o termcaps.o
DATA= COMPILING HACKING bugs.text cannibalism.log \
chocolate-cake.text crazy.log gameplay.text \
snake-colours.sh snake.1 spoilers.text \
termcaps.c terminals.text troubleshooting.text
DATA= COMPILING HACKING bugs.md cannibalism.log \
chocolate-cake.md crazy.log gameplay.md \
snake-colours.sh snake.1 spoilers.md \
termcaps.c terminals.md troubleshooting.md
TARGET= prog snake snake-colours play snake-colours termcaps ${ALT_TARGET}
#
ALT_OBJ=
2020/ferguson1/README.md
+16 -16
View File
@@ -37,19 +37,19 @@ This game has a number of configurable pitfalls including walls and snakes.
There is a good deal of useful documentation that is provided with this entry:
* gameplay.markdown ([gameplay.html][])
* gameplay.md ([gameplay.html][])
Documented game *features*!
* terminals.markdown ([terminals.html][])
* terminals.md ([terminals.html][])
Information about terminal capabilities, dimensions (setting and how to restore sanity if it causes any problems) as well as colours (limitations etc.).
* troubleshooting.markdown ([troubleshooting.html][])
* troubleshooting.md ([troubleshooting.html][])
Workaround for various game *features*
* bugs.markdown ([bugs.html][])
* bugs.md ([bugs.html][])
Bugs and things that might seem like bugs but are not.
@@ -75,7 +75,7 @@ Snake has two cheat modes (passable walls and self [cannibalism]), a drawing (or
practising) mode, *can play by itself (**and win!**)*, is coloured (included
[snake-colours.sh][] and [play.sh][] scripts compile in player-selected
colours) and there are many other play modes (many more can be devised with the
imagination and the environmental variables; see [gameplay.markdown][] /
imagination and the environmental variables; see [gameplay.md][] /
[gameplay.html][] for many examples) and options. You can pause and there's
even a built-in test unit for some features! The following variables change the
game in the following ways (all can be combined):
@@ -112,16 +112,16 @@ game in the following ways (all can be combined):
included in the relevant section (this goes for a low **EVADE** value too).
* Grow-Shrink mode (Positive and Negative Winning) mode (see
[gameplay.markdown][] for more details).
[gameplay.md][] for more details).
* The dimensions of the game (this is actually a terminal thing but I document
how to do this and its potential pitfalls) (**LINES** , **COLUMNS**).
There are no complicated command line invocations; it's just a matter of passing
into the game descriptively named variables and I include a script that sets up
many different gameplay modes ([gameplay.markdown][] and [play.sh][]).
many different gameplay modes ([gameplay.md][] and [play.sh][]).
The [gameplay.markdown][] ([gameplay.html][]) file has all the information on
The [gameplay.md][] ([gameplay.html][]) file has all the information on
what the game looks like, how to play, the different types of modes (that I have
thought of so far) including all those in the above list. Along with the
[play.sh][] and [snake-colours.sh][] scripts it's probably the most important
@@ -139,18 +139,18 @@ Probably just as important is [chocolate-cake.html][] with an old but wonderful
recipe (because the judges love chocolate and who can blame them? - also it goes
with one of the IAQs I include later).
The [troubleshooting.markdown][] ([troubleshooting.html][]) file has some advice
The [troubleshooting.md][] ([troubleshooting.html][]) file has some advice
on potential problems (and things that might appear to be problems at first
glance but are not) that I have thought of or encountered.
The [terminals.markdown][] ([terminals.html][]) has a variety of information
The [terminals.md][] ([terminals.html][]) has a variety of information
specific to terminals from input/directions, dimensions, sanity and colours: a
sort of troubleshooting guide for terminals with some additional information.
The [spoilers.markdown][] has a variety of information including some of the
obfuscation techniques and a bit of how it works.
The [bugs.markdown][] ([bugs.html][]) has a list of known bugs and things that
The [bugs.md][] ([bugs.html][]) has a list of known bugs and things that
look like bugs but aren't as well as documenting a built-in test unit for some
features.
@@ -222,7 +222,7 @@ and [troubleshooting.html][] - along with the most important one
took fewer bytes and the negative shedding is a positive consequence of
unsigned arithmetic.
On a more serious note look at [bugs.markdown][] ([bugs.html][]).
On a more serious note look at [bugs.md][] ([bugs.html][]).
### <a name="naqs" href="#toc">NAQs/IAQs (Never/Infrequently Asked Questions)</a>
@@ -453,18 +453,18 @@ both do.
[COMPILING]: COMPILING
[HACKING]: HACKING
[bugs.markdown]: bugs.markdown
[bugs.md]: bugs.md
[bugs.html]: bugs.html
[troubleshooting.markdown]: troubleshooting.markdown
[troubleshooting.md]: troubleshooting.md
[troubleshooting.html]: troubleshooting.html
[human snakes]: http://www.macroevolution.net/snake-human-hybrids.html
[chocolate-cake.html]: chocolate-cake.html
[spoilers.markdown]: spoilers.markdown
[terminals.markdown]: terminals.markdown
[terminals.md]: terminals.md
[Surround]: https://en.wikipedia.org/wiki/Surround_(video_game)
[Snake walk: The physics of slithering]: https://www.bbc.co.uk/news/science-environment-35563941
[snake-colours.sh]: snake-colours.sh
[gameplay.markdown]: gameplay.markdown
[gameplay.md]: gameplay.md
[gameplay.html]: gameplay.html
[flying snakes]: https://www.bbc.co.uk/news/science-environment-25943693
[play.sh]: play.sh
2020/ferguson1/bugs.html
+2 -2
View File
@@ -153,7 +153,7 @@ way negative size will force a win.</p>
head several places until you end up getting to the max size (by way of it
being unsigned). This isn&rsquo;t a bug even if it might seem like one. In fact
this is the basis of the grow/shrink mode of play that I talk about in the
<a href="gameplay.markdown">gameplay.markdown</a> (<a href="gameplay.html">gameplay.html</a>) file.</p>
<a href="gameplay.md">gameplay.md</a> (<a href="gameplay.html">gameplay.html</a>) file.</p>
<p>Here&rsquo;s another thing to be aware of. Let&rsquo;s say you do:</p>
@@ -270,7 +270,7 @@ that 49 is the max snake size. How is this derived and why?</p>
(<code>playable_rows * playable_columns</code>). I have played with this many
times and I do not believe there should be a problem. If there is it&rsquo;s from a
very poor implementation of rand() and I discuss this in
<a href="troubleshooting.markdown">troubleshooting.markdown</a> (<a href="troubleshooting.html">troubleshooting.html</a>).</p>
<a href="troubleshooting.md">troubleshooting.md</a> (<a href="troubleshooting.html">troubleshooting.html</a>).</p>
<p>There I also give some test outputs without the cap in place to give an idea of
when it became a problem (or would have). In short this is known but I do not
2020/ferguson1/bugs.markdown
+4 -4
View File
@@ -120,7 +120,7 @@ And you'll see that you start to be the normal size but then you leave your
head several places until you end up getting to the max size (by way of it
being unsigned). This isn't a bug even if it might seem like one. In fact
this is the basis of the grow/shrink mode of play that I talk about in the
[gameplay.markdown][] ([gameplay.html][]) file.
[gameplay.md][] ([gameplay.html][]) file.
Here's another thing to be aware of. Let's say you do:
@@ -232,7 +232,7 @@ With 10 rows and columns it's calculated as 7 * 7 (i.e. it's
(`playable_rows * playable_columns`). I have played with this many
times and I do not believe there should be a problem. If there is it's from a
very poor implementation of rand() and I discuss this in
[troubleshooting.markdown][] ([troubleshooting.html][]).
[troubleshooting.md][] ([troubleshooting.html][]).
There I also give some test outputs without the cap in place to give an idea of
when it became a problem (or would have). In short this is known but I do not
@@ -285,8 +285,8 @@ but it is very much appreciated and it means a great deal to me. Cheers.)
[crazy.log]: crazy.log
[gameplay.markdown]: gameplay.markdown
[troubleshooting.markdown]: troubleshooting.markdown
[gameplay.md]: gameplay.md
[troubleshooting.md]: troubleshooting.md
[troubleshooting.html]: troubleshooting.html
[gameplay.html]: gameplay.html
[cannibalism.log]: cannibalism.log
2020/ferguson1/bugs.text → 2020/ferguson1/bugs.md
+4 -4
View File
@@ -130,7 +130,7 @@ And you'll see that you start to be the normal size but then you leave your
head several places until you end up getting to the max size (by way of it
being unsigned). This isn't a bug even if it might seem like one. In fact
this is the basis of the grow/shrink mode of play that I talk about in the
[gameplay.markdown][] ([gameplay.html][]) file.
[gameplay.md][] ([gameplay.html][]) file.
Here's another thing to be aware of. Let's say you do:
@@ -242,7 +242,7 @@ With 10 rows and columns it's calculated as 7 * 7 (i.e. it's
(`playable_rows * playable_columns`). I have played with this many
times and I do not believe there should be a problem. If there is it's from a
very poor implementation of rand() and I discuss this in
[troubleshooting.markdown][] ([troubleshooting.html][]).
[troubleshooting.md][] ([troubleshooting.html][]).
There I also give some test outputs without the cap in place to give an idea of
when it became a problem (or would have). In short this is known but I do not
@@ -295,8 +295,8 @@ but it is very much appreciated and it means a great deal to me. Cheers.)
[crazy.log]: crazy.log
[gameplay.markdown]: gameplay.markdown
[troubleshooting.markdown]: troubleshooting.markdown
[gameplay.md]: gameplay.md
[troubleshooting.md]: troubleshooting.md
[troubleshooting.html]: troubleshooting.html
[gameplay.html]: gameplay.html
[cannibalism.log]: cannibalism.log
2020/ferguson1/chocolate-cake.text → 2020/ferguson1/chocolate-cake.md
View File
File renamed without changes.
2020/ferguson1/gameplay.html
+5 -5
View File
@@ -87,11 +87,11 @@ for the input keys.</p>
<h1>1. <a name="support" href="#toc">Testing terminal environment/capabilities</a></h1>
<p>Most people probably won&rsquo;t have any issue at all but for those who have any
problems with the terminal see the <a href="terminals.markdown">terminals.markdown</a> file for more
problems with the terminal see the <a href="terminals.md">terminals.md</a> file for more
information on the terminal capabilities testing utility I include.</p>
<p>For troubleshooting other problems see <a href="troubleshooting.markdown">troubleshooting.markdown</a>
(<a href="troubleshooting.html">troubleshooting.html</a>) and <a href="bugs.markdown">bugs.markdown</a> (<a href="bugs.html">bugs.html</a>).</p>
<p>For troubleshooting other problems see <a href="troubleshooting.md">troubleshooting.md</a>
(<a href="troubleshooting.html">troubleshooting.html</a>) and <a href="bugs.md">bugs.md</a> (<a href="bugs.html">bugs.html</a>).</p>
<h1>2. <a name="input" href="#toc">Input keys</a></h1>
@@ -441,7 +441,7 @@ less than again - I&rsquo;m not going to try and figure that out however). Anywa
</code></pre>
<p>Observe that the size isn&rsquo;t the default 997: because the screen size is too
small for that value (see <a href="terminals.markdown">terminals.markdown</a>).</p>
small for that value (see <a href="terminals.md">terminals.md</a>).</p>
<p>The reason I chose 997 is that it leaves a bit of a challenge for some (maybe
most) people but it&rsquo;s still winnable. Previously even I couldn&rsquo;t have won unless
@@ -471,7 +471,7 @@ the game is won is 199 - also a prime!</p>
<h1>4. <a name="modes" href="#toc">Gameplay modes</a></h1>
<p>Here I list a number of different modes of play. In the <a href="bugs.markdown">bugs.markdown</a>
<p>Here I list a number of different modes of play. In the <a href="bugs.md">bugs.md</a>
(<a href="bugs.html">bugs.html</a>) file I even show how there&rsquo;s a built-in test unit for some
modes! There are certainly other modes that could be imagined: the modes below
happened over time and some were simply an accidental discovery or something I
2020/ferguson1/gameplay.markdown
+8 -8
View File
@@ -36,11 +36,11 @@ for the input keys.
# 1. <a name="support" href="#toc">Testing terminal environment/capabilities</a>
Most people probably won't have any issue at all but for those who have any
problems with the terminal see the [terminals.markdown][] file for more
problems with the terminal see the [terminals.md][] file for more
information on the terminal capabilities testing utility I include.
For troubleshooting other problems see [troubleshooting.markdown][]
([troubleshooting.html][]) and [bugs.markdown][] ([bugs.html][]).
For troubleshooting other problems see [troubleshooting.md][]
([troubleshooting.html][]) and [bugs.md][] ([bugs.html][]).
# 2. <a name="input" href="#toc">Input keys</a>
@@ -390,7 +390,7 @@ less than again - I'm not going to try and figure that out however). Anyway:
X:24/49 Y:8/16 S:658/658 B:0
Observe that the size isn't the default 997: because the screen size is too
small for that value (see [terminals.markdown][]).
small for that value (see [terminals.md][]).
The reason I chose 997 is that it leaves a bit of a challenge for some (maybe
most) people but it's still winnable. Previously even I couldn't have won unless
@@ -422,7 +422,7 @@ If you wish to quit you can hit 'q' (case-insensitive). For example:
# 4. <a name="modes" href="#toc">Gameplay modes</a>
Here I list a number of different modes of play. In the [bugs.markdown][]
Here I list a number of different modes of play. In the [bugs.md][]
([bugs.html][]) file I even show how there's a built-in test unit for some
modes! There are certainly other modes that could be imagined: the modes below
happened over time and some were simply an accidental discovery or something I
@@ -771,11 +771,11 @@ the imagination and creativity almost anything is possible.** This is something
they believe in themselves!** I would have never thought this the case for me
years ago but I know it's true now. **Believe in yourself. Always.**
[terminals.markdown]: terminals.markdown
[terminals.md]: terminals.md
[terminals.html]: terminals.html
[troubleshooting.markdown]: troubleshooting.markdown
[troubleshooting.md]: troubleshooting.md
[troubleshooting.html]: troubleshooting.html
[bugs.markdown]: bugs.markdown
[bugs.md]: bugs.md
[bugs.html]: bugs.html
[spoilers.markdown]: spoilers.markdown
[snake-colours]: snake-colours
2020/ferguson1/gameplay.text → 2020/ferguson1/gameplay.md
+8 -8
View File
@@ -69,11 +69,11 @@ for the input keys.
# 1. <a name="support" href="#toc">Testing terminal environment/capabilities</a>
Most people probably won't have any issue at all but for those who have any
problems with the terminal see the [terminals.markdown][] file for more
problems with the terminal see the [terminals.md][] file for more
information on the terminal capabilities testing utility I include.
For troubleshooting other problems see [troubleshooting.markdown][]
([troubleshooting.html][]) and [bugs.markdown][] ([bugs.html][]).
For troubleshooting other problems see [troubleshooting.md][]
([troubleshooting.html][]) and [bugs.md][] ([bugs.html][]).
# 2. <a name="input" href="#toc">Input keys</a>
@@ -423,7 +423,7 @@ less than again - I'm not going to try and figure that out however). Anyway:
X:24/49 Y:8/16 S:658/658 B:0
Observe that the size isn't the default 997: because the screen size is too
small for that value (see [terminals.markdown][]).
small for that value (see [terminals.md][]).
The reason I chose 997 is that it leaves a bit of a challenge for some (maybe
most) people but it's still winnable. Previously even I couldn't have won unless
@@ -455,7 +455,7 @@ If you wish to quit you can hit 'q' (case-insensitive). For example:
# 4. <a name="modes" href="#toc">Gameplay modes</a>
Here I list a number of different modes of play. In the [bugs.markdown][]
Here I list a number of different modes of play. In the [bugs.md][]
([bugs.html][]) file I even show how there's a built-in test unit for some
modes! There are certainly other modes that could be imagined: the modes below
happened over time and some were simply an accidental discovery or something I
@@ -804,11 +804,11 @@ the imagination and creativity almost anything is possible.** This is something
they believe in themselves!** I would have never thought this the case for me
years ago but I know it's true now. **Believe in yourself. Always.**
[terminals.markdown]: terminals.markdown
[terminals.md]: terminals.md
[terminals.html]: terminals.html
[troubleshooting.markdown]: troubleshooting.markdown
[troubleshooting.md]: troubleshooting.md
[troubleshooting.html]: troubleshooting.html
[bugs.markdown]: bugs.markdown
[bugs.md]: bugs.md
[bugs.html]: bugs.html
[spoilers.markdown]: spoilers.markdown
[snake-colours]: snake-colours
2020/ferguson1/snake.1
+9 -9
View File
@@ -4,7 +4,7 @@ snake \- Feature\-rich curses implementation of the classic 'Snake' game with ma
.SH SYNOPSIS
\fBsnake\fP
.SH DESCRIPTION
\fBsnake\fP has two cheat modes (passable walls/self[cannibalism]), a drawing/practising mode, \fIcan play by itself\fP (\fBand win!\fP), is coloured (included \fIsnake-colours.sh\fP and \fIplay.sh\fP scripts compile in player\-selected colours) and there are many other play modes (many more can be devised with the imagination and the environmental variables; see \fbENVIRONMENT\fP and the file \fIgameplay.markdown\fP for many examples) and options.
\fBsnake\fP has two cheat modes (passable walls/self[cannibalism]), a drawing/practising mode, \fIcan play by itself\fP (\fBand win!\fP), is coloured (included \fIsnake-colours.sh\fP and \fIplay.sh\fP scripts compile in player\-selected colours) and there are many other play modes (many more can be devised with the imagination and the environmental variables; see \fbENVIRONMENT\fP and the file \fIgameplay.md\fP for many examples) and options.
You can pause and there's even a built\-in test unit for some features!
Some of the configurable features are:
.PP
@@ -50,11 +50,11 @@ This is how snakes grow in the wild so is a misnomer here because snakes don't g
.PP
.RS
\fB\-\fP Computer plays the game (\fBWAIT=0\fP)
\fB(EPILEPSY/STIMULATION OVERLOAD TRIGGER WARNING\fP included in the relevant section of the \fIgameplay.markdown\fP; this goes for low \fBEVADE\fP values too).
\fB(EPILEPSY/STIMULATION OVERLOAD TRIGGER WARNING\fP included in the relevant section of the \fIgameplay.md\fP; this goes for low \fBEVADE\fP values too).
.RE
.PP
.RS
\fB\-\fP Grow\-Shrink (Positive and Negative Winning) mode (see \fIgameplay.markdown\fP for more details).
\fB\-\fP Grow\-Shrink (Positive and Negative Winning) mode (see \fIgameplay.md\fP for more details).
.RE
.PP
.RS
@@ -160,15 +160,15 @@ Source file to the Snake game (IOCCC entry source file).
Describes what the entry (game) is, what it looks like, how to play etc.
Includes a variety of other information as well as NAQs (never asked questions that I believe could actually be asked so perhaps better would be infrequently asked questions, IAQs).
.RE
\fIgameplay.markdown\fP
\fIgameplay.md\fP
.RS
Includes information on how to play, demonstrates some of the features and describes many gameplay modes.
.RE
\fItroubleshooting.markdown\fP
\fItroubleshooting.md\fP
.RS
Information to help work out any possible problems as well as show how to configure and restore terminal dimensions for the game.
.RE
\fIterminals.markdown\fP
\fIterminals.md\fP
.RS
A troubleshooting guide focusing more on terminals.
.RE
@@ -193,7 +193,7 @@ To build the terminal capabilities test utility and the Snake game itself.
.RS
Helper script to compile the game with player selected colours.
.RE
\fIbugs.markdown\fP
\fIbugs.md\fP
.RS
List of bugs and things that might appear to be bugs that aren't, were once bugs etc.
.RE
@@ -247,7 +247,7 @@ Also snakes grow by moulting (technical term for shedding) so when the snake lea
It's a misnomer: it took fewer bytes and the negative shedding is a positive consequence of unsigned arithmetic.
.RE
.PP
On a more serious note see the \fBbugs.markdown\fP file.
On a more serious note see the \fBbugs.md\fP file.
.SH EXAMPLES
.PP
Test your terminal capabilities and get other various data (based on dimensions of terminal, growth size, size and max size as specified i.e. you can pass in the variables \fBLINES\fP, \fBCOLUMNS\fP, \fBMAXSIZE\fP, \fBGROW\fP and \fBSIZE\fp):
@@ -295,7 +295,7 @@ Run script that prompts for the colours to be used, compiles and then runs the g
.PP
That will compile the game to be the colours you select and then enable cannibalism, set the starting size to 15, max size to 45 and walls are made impassable.
.PP
For more gameplay information and modes check \fIgameplay.markdown\fP; and for an interactive script that prompts for some of those modes see the \fIplay.sh\fP script.
For more gameplay information and modes check \fIgameplay.md\fP; and for an interactive script that prompts for some of those modes see the \fIplay.sh\fP script.
.SH AUTHOR
Written by Cody Boone Ferguson for IOCCC 2020 (the 27th IOCCC).
.SH SEE ALSO
2020/ferguson1/spoilers.html
+1 -1
View File
@@ -27,7 +27,7 @@
<h1>Introduction (SPOILER ALERT)</h1>
<p>In the <a href="gameplay.markdown">gameplay.markdown</a> (<a href="gameplay.html">gameplay.html</a>) file I have given enough
<p>In the <a href="gameplay.md">gameplay.md</a> (<a href="gameplay.html">gameplay.html</a>) file I have given enough
information to know how the game looks, how to move the snake, how to pause etc.
In this file I am including (some) information on how the game actually works:
the technical details as it were, obfuscation techniques and also some of the
2020/ferguson1/spoilers.markdown
+2 -2
View File
@@ -1,6 +1,6 @@
# Introduction (SPOILER ALERT)
In the [gameplay.markdown][] ([gameplay.html][]) file I have given enough
In the [gameplay.md][] ([gameplay.html][]) file I have given enough
information to know how the game looks, how to move the snake, how to pause etc.
In this file I am including (some) information on how the game actually works:
the technical details as it were, obfuscation techniques and also some of the
@@ -927,7 +927,7 @@ display something, it squeezes a few more bytes and having a space is hardly an
imposition on usage (and for that matter having a 'o' at 0,0 isn't either).
[gameplay.markdown]: gameplay.markdown
[gameplay.md]: gameplay.md
[gameplay.html]: gameplay.html
[COMPILING]: COMPILING
[HACKING]: HACKING
2020/ferguson1/spoilers.text → 2020/ferguson1/spoilers.md
+2 -2
View File
@@ -1,6 +1,6 @@
# Introduction (SPOILER ALERT)
In the [gameplay.markdown][] ([gameplay.html][]) file I have given enough
In the [gameplay.md][] ([gameplay.html][]) file I have given enough
information to know how the game looks, how to move the snake, how to pause etc.
In this file I am including (some) information on how the game actually works:
the technical details as it were, obfuscation techniques and also some of the
@@ -937,7 +937,7 @@ display something, it squeezes a few more bytes and having a space is hardly an
imposition on usage (and for that matter having a 'o' at 0,0 isn't either).
[gameplay.markdown]: gameplay.markdown
[gameplay.md]: gameplay.md
[gameplay.html]: gameplay.html
[COMPILING]: COMPILING
[HACKING]: HACKING
2020/ferguson1/terminals.text → 2020/ferguson1/terminals.md
View File
File renamed without changes.
2020/ferguson1/troubleshooting.html
+3 -3
View File
@@ -107,7 +107,7 @@ e.g. when the snake is growing.</p>
<p> Sometimes also it might appear that the movement is delayed but there are
numerous causes for this some of which are a busy computer but ultimately
it&rsquo;ll catch up; just give it the time it needs.</p></li>
<li><p>BOTTOM LINE: If you want more information then see the <a href="bugs.markdown">bugs.markdown</a> file.</p></li>
<li><p>BOTTOM LINE: If you want more information then see the <a href="bugs.md">bugs.md</a> file.</p></li>
</ul>
@@ -323,7 +323,7 @@ so that&rsquo;s probably why; in CentOS I did have to install it specially.</p>
eat too many bytes in the entry (I cite the functions in the HACKING file).</p>
<p> I discuss colours and terminals in much more detail in
<a href="terminals.markdown">terminals.markdown</a> (<a href="terminals.html">terminals.html</a>).</p></li>
<a href="terminals.md">terminals.md</a> (<a href="terminals.html">terminals.html</a>).</p></li>
</ul>
@@ -423,7 +423,7 @@ example</p>
0.</p>
<p>I discuss the signed/unsigned issue to do with curses and sizes in C being
unsigned in <a href="bugs.markdown">bugs.markdown</a> but probably there isn&rsquo;t anything more to say here.</p>
unsigned in <a href="bugs.md">bugs.md</a> but probably there isn&rsquo;t anything more to say here.</p>
<h2><a name="errors" href="#toc">Errors and error reporting</a></h2>
2020/ferguson1/troubleshooting.markdown
+5 -5
View File
@@ -78,7 +78,7 @@ e.g. when the snake is growing.
numerous causes for this some of which are a busy computer but ultimately
it'll catch up; just give it the time it needs.
* BOTTOM LINE: If you want more information then see the [bugs.markdown][] file.
* BOTTOM LINE: If you want more information then see the [bugs.md][] file.
## <a name="invisiblehead" href="#toc">I can't see the snake head (or other part of the snake)!</a>
@@ -286,7 +286,7 @@ so that's probably why; in CentOS I did have to install it specially.
eat too many bytes in the entry (I cite the functions in the HACKING file).
I discuss colours and terminals in much more detail in
[terminals.markdown][] ([terminals.html][]).
[terminals.md][] ([terminals.html][]).
## <a name="toodark" href="#toc">The text is hard to see (not bright enough)!</a>
@@ -376,7 +376,7 @@ Is invalid input because octal only has digits 0 - 7: the resulting size will be
I discuss the signed/unsigned issue to do with curses and sizes in C being
unsigned in [bugs.markdown][] but probably there isn't anything more to say here.
unsigned in [bugs.md][] but probably there isn't anything more to say here.
## <a name="errors" href="#toc">Errors and error reporting</a>
@@ -416,8 +416,8 @@ is 0 and I limit the size to be no bigger than the max size.
[HACKING]: HACKING
[prog.c]: prog.c
[bugs.markdown]: bugs.markdown
[terminals.markdown]: terminals.markdown
[bugs.md]: bugs.md
[terminals.md]: terminals.md
[terminals.html]: terminals.html
[snake-colours]: snake-colours
[Snakey]: https://www.hp-lexicon.org/character/gaunt-family/morfin-gaunt/
2020/ferguson1/troubleshooting.text → 2020/ferguson1/troubleshooting.md
+17 -5
View File
@@ -9,18 +9,30 @@ it as structured as possible/easiest to find.
<a name="toc"></a>
- [The top wall isn't (all/some of the time) 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 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)
- [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)
## <a name="topwall" href="#toc">The top wall isn't (all/some of the time) visible!</a>
Because the score line is dynamic in length depending on the terminal size it
@@ -78,7 +90,7 @@ e.g. when the snake is growing.
numerous causes for this some of which are a busy computer but ultimately
it'll catch up; just give it the time it needs.
* BOTTOM LINE: If you want more information then see the [bugs.markdown][] file.
* BOTTOM LINE: If you want more information then see the [bugs.md][] file.
## <a name="invisiblehead" href="#toc">I can't see the snake head (or other part of the snake)!</a>
@@ -286,7 +298,7 @@ so that's probably why; in CentOS I did have to install it specially.
eat too many bytes in the entry (I cite the functions in the HACKING file).
I discuss colours and terminals in much more detail in
[terminals.markdown][] ([terminals.html][]).
[terminals.md][] ([terminals.html][]).
## <a name="toodark" href="#toc">The text is hard to see (not bright enough)!</a>
@@ -376,7 +388,7 @@ Is invalid input because octal only has digits 0 - 7: the resulting size will be
I discuss the signed/unsigned issue to do with curses and sizes in C being
unsigned in [bugs.markdown][] but probably there isn't anything more to say here.
unsigned in [bugs.md][] but probably there isn't anything more to say here.
## <a name="errors" href="#toc">Errors and error reporting</a>
@@ -416,8 +428,8 @@ is 0 and I limit the size to be no bigger than the max size.
[HACKING]: HACKING
[prog.c]: prog.c
[bugs.markdown]: bugs.markdown
[terminals.markdown]: terminals.markdown
[bugs.md]: bugs.md
[terminals.md]: terminals.md
[terminals.html]: terminals.html
[snake-colours]: snake-colours
[Snakey]: https://www.hp-lexicon.org/character/gaunt-family/morfin-gaunt/