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

fix internal links in entry index.html from 1984 thru 2012

Browse Source
This commit is contained in:
Landon Curt Noll committed 2024-04-22 03:17:20 -07:00
1 parent 2da0a6c05f
commit 99cd17401e
151 files changed
+360 -360
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

1998/banks/README.md
+9 -9
View File
@@ -28,7 +28,7 @@ on this in the author's comments in the [Alternate Build
Instructions](#alternate-build-instructions) section.
If however you wish to change the above controls, see the header file
[keysym.h](keysym.h) for the definitions of other characters that you might wish
[keysym.h](%%REPO_URL%%/1998/banks/keysym.h) for the definitions of other characters that you might wish
to use. The name of the macro in the header file is what you need to set the
macros to, depending on what controls you wish to redefine. For instance, to set
the throttle up and down to `u` and `d`:
@@ -46,7 +46,7 @@ corresponds to `d`:
#define XK_u 0x0075 /* U+0075 LATIN SMALL LETTER U */
```
Note that the [keysym.h](keysym.h) file is not complete from X11; it's just the
Note that the [keysym.h](%%REPO_URL%%/1998/banks/keysym.h) file is not complete from X11; it's just the
more likely candidates (and some that are probably unlikely :-) ).
The upper case letters would be `XK_U` and `XK_D` and you can search the header
@@ -200,31 +200,31 @@ less than 1000 total lines of input.
Here is a brief description of the scenery files:
- [horizon.sc](horizon.sc)
- [horizon.sc](%%REPO_URL%%/1998/banks/horizon.sc)
A horizon, nothing more. You will probably always want to input this piece
of scenery.
- [mountains.sc](mountains.sc)
- [mountains.sc](%%REPO_URL%%/1998/banks/mountains.sc)
An alternate horizon; a little more mountainous.
- [pittsburgh.sc]([pittsburgh.sc])
- [pittsburgh.sc](%%REPO_URL%%/1998/banks/pittsburgh.sc)
Scenery of downtown Pittsburgh. The downtown area is initially located
to your right.
- [bb.sc](bb.sc)
- [bb.sc](%%REPO_URL%%/1998/banks/bb.sc)
Simple obstacle course. Try to fly over the buildings and under the
bridges.
- [pyramids.sc](pyramids.sc)
- [pyramids.sc](1998/banks/pyramids.sc)
Fly over the tombs of the ancient Pharaohs, in this (fictitious) Egyptian
landscape.
- [river.sc](river.sc)
- [river.sc](%%REPO_URL%%/1998/banks/river.sc)
Follow a flowing river from the sky.
@@ -261,7 +261,7 @@ I'm sure you'll be making your own scenery files very soon!!!
### Alternate Build Instructions
Several options must be passed to the compiler to make the build
work. The provided [Makefile](Makefile) has the appropriate options set
work. The provided [Makefile](%%REPO_URL%%/1998/banks/Makefile) has the appropriate options set
to default values. Use this section if you want to compile with
different options.
1998/banks/index.html
+9 -9
View File
@@ -172,7 +172,7 @@ default value. The author provided the following table:</p>
on this in the author’s comments in the <a href="#alternate-build-instructions">Alternate Build
Instructions</a> section.</p>
<p>If however you wish to change the above controls, see the header file
<a href="keysym.h">keysym.h</a> for the definitions of other characters that you might wish
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/keysym.h">keysym.h</a> for the definitions of other characters that you might wish
to use. The name of the macro in the header file is what you need to set the
macros to, depending on what controls you wish to redefine. For instance, to set
the throttle up and down to <code>u</code> and <code>d</code>:</p>
@@ -181,7 +181,7 @@ the throttle up and down to <code>u</code> and <code>d</code>:</p>
corresponds to <code>d</code>:</p>
<pre><code> #define XK_d 0x0064 /* U+0064 LATIN SMALL LETTER D */
#define XK_u 0x0075 /* U+0075 LATIN SMALL LETTER U */</code></pre>
<p>Note that the <a href="keysym.h">keysym.h</a> file is not complete from X11; it’s just the
<p>Note that the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/keysym.h">keysym.h</a> file is not complete from X11; it’s just the
more likely candidates (and some that are probably unlikely :-) ).</p>
<p>The upper case letters would be <code>XK_U</code> and <code>XK_D</code> and you can search the header
file for ‘LATIN CAPITAL D’, for example.</p>
@@ -283,21 +283,21 @@ You may input more than one scenery file, as long as there are
less than 1000 total lines of input.</p>
<p>Here is a brief description of the scenery files:</p>
<ul>
<li><p><a href="horizon.sc">horizon.sc</a></p>
<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/horizon.sc">horizon.sc</a></p>
<p>A horizon, nothing more. You will probably always want to input this piece
of scenery.</p></li>
<li><p><a href="mountains.sc">mountains.sc</a></p>
<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/mountains.sc">mountains.sc</a></p>
<p>An alternate horizon; a little more mountainous.</p></li>
<li><p><a href="%5Bpittsburgh.sc%5D">pittsburgh.sc</a></p>
<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/pittsburgh.sc">pittsburgh.sc</a></p>
<p>Scenery of downtown Pittsburgh. The downtown area is initially located
to your right.</p></li>
<li><p><a href="bb.sc">bb.sc</a></p>
<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/bb.sc">bb.sc</a></p>
<p>Simple obstacle course. Try to fly over the buildings and under the
bridges.</p></li>
<li><p><a href="pyramids.sc">pyramids.sc</a></p>
<li><p><a href="1998/banks/pyramids.sc">pyramids.sc</a></p>
<p>Fly over the tombs of the ancient Pharaohs, in this (fictitious) Egyptian
landscape.</p></li>
<li><p><a href="river.sc">river.sc</a></p>
<li><p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/river.sc">river.sc</a></p>
<p>Follow a flowing river from the sky.</p></li>
</ul>
<p>A few examples of how to input scenery:</p>
@@ -316,7 +316,7 @@ positive altitudes</em>.</p>
<p>I’m sure you’ll be making your own scenery files very soon!!!</p>
<h3 id="alternate-build-instructions">Alternate Build Instructions</h3>
<p>Several options must be passed to the compiler to make the build
work. The provided <a href="Makefile">Makefile</a> has the appropriate options set
work. The provided <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/banks/Makefile">Makefile</a> has the appropriate options set
to default values. Use this section if you want to compile with
different options.</p>
<p>To map a key to a control, you must pass an option to the
1998/dlowe/README.md
+3 -3
View File
@@ -118,17 +118,17 @@ A CGI script such as:
```
can be used to pootify web pages. This has been added as
[pootify.cgi.sh](pootify.cgi.sh) which forbids `file://` based URLs and which
[pootify.cgi.sh](%%REPO_URL%%/1998/dlowe/pootify.cgi.sh) which forbids `file://` based URLs and which
uses `lynx(1)` with the option referred to above. This will not, of course,
render it as html but rather show the modified html. Nevertheless, this has
**NOT** been tested as a CGI script with a webserver to display a pootified web
page.
The [pootify.sh](pootify.sh) script has also been added which is a modification
The [pootify.sh](%%REPO_URL%%/1998/dlowe/pootify.sh) script has also been added which is a modification
to the above script which can be used to render html files locally with the
added bonus that one can use `file://` URLs. If one wants a CGI script they
should use the above one instead. You can use the script
[pootify.sh](pootify.sh), however, to download and generate html files that you
[pootify.sh](%%REPO_URL%%/1998/dlowe/pootify.sh), however, to download and generate html files that you
can look at locally in a browser or pipe through `less(1)`. For instance:
``` <!---sh-->
1998/dlowe/index.html
+3 -3
View File
@@ -213,16 +213,16 @@ more consistent level of quality. :-)</p>
fi
fi</code></pre>
<p>can be used to pootify web pages. This has been added as
<a href="pootify.cgi.sh">pootify.cgi.sh</a> which forbids <code>file://</code> based URLs and which
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dlowe/pootify.cgi.sh">pootify.cgi.sh</a> which forbids <code>file://</code> based URLs and which
uses <code>lynx(1)</code> with the option referred to above. This will not, of course,
render it as html but rather show the modified html. Nevertheless, this has
<strong>NOT</strong> been tested as a CGI script with a webserver to display a pootified web
page.</p>
<p>The <a href="pootify.sh">pootify.sh</a> script has also been added which is a modification
<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dlowe/pootify.sh">pootify.sh</a> script has also been added which is a modification
to the above script which can be used to render html files locally with the
added bonus that one can use <code>file://</code> URLs. If one wants a CGI script they
should use the above one instead. You can use the script
<a href="pootify.sh">pootify.sh</a>, however, to download and generate html files that you
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dlowe/pootify.sh">pootify.sh</a>, however, to download and generate html files that you
can look at locally in a browser or pipe through <code>less(1)</code>. For instance:</p>
<pre><code> ./pootify.sh URL=https://microsoft.com | less
1998/dorssel/README.md
+2 -2
View File
@@ -45,7 +45,7 @@ altering the behavior ?
### Extra credit:
Try doing what the last part of the last command in [try.sh](try.sh) suggests.
Try doing what the last part of the last command in [try.sh](%%REPO_URL%%/1998/dorssel/try.sh) suggests.
As in, do the following:
``` <!---sh-->
@@ -111,7 +111,7 @@ is the same as
./dorssel < dorssel.c | ./dorssel
```
- The file [dorssel.md](dorssel.md) contains all the information needed to
- The file [dorssel.html](dorssel.html) contains all the information needed to
understand this program. For an obfuscated spoiler, try
``` <!---sh-->
1998/dorssel/index.html
+2 -2
View File
@@ -176,7 +176,7 @@ what values may they be changed without altering the behavior?</p></li>
altering the behavior ?</p></li>
</ul>
<h3 id="extra-credit">Extra credit:</h3>
<p>Try doing what the last part of the last command in <a href="try.sh">try.sh</a> suggests.
<p>Try doing what the last part of the last command in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/dorssel/try.sh">try.sh</a> suggests.
As in, do the following:</p>
<pre><code> echo &quot;. -..- . .-. -.-. .. ... .
-.-. .... .- -. --. . - .... . .--. .-. --- --. .-. .- -- ... --- .. - -.. --- . ... -. --- - ... .... --- ..- -&quot; | ./dorssel</code></pre>
@@ -218,7 +218,7 @@ text that can be reversibly Morsified, i.e.</li>
<p>is the same as</p>
<pre><code> ./dorssel &lt; dorssel.c | ./dorssel</code></pre>
<ul>
<li>The file <a href="dorssel.md">dorssel.md</a> contains all the information needed to
<li>The file <a href="dorssel.html">dorssel.html</a> contains all the information needed to
understand this program. For an obfuscated spoiler, try</li>
</ul>
<pre><code> ./dorssel &lt; dorssel.md</code></pre>
1998/fanf/README.md
+3 -3
View File
@@ -28,7 +28,7 @@ Enter an expression on standard input. To try some we have selected:
### Historical aside:
At a time the code in [fanf.c](fanf.c) was that of [fanf.orig.c](fanf.orig.c)
At a time the code in [fanf.c](%%REPO_URL%%/1998/fanf/fanf.c) was that of [fanf.orig.c](fanf.orig.c)
but to get this to compile in modern systems it had to be translated to what you
now see. The intermediate steps can still be performed but they might be
different from the past. This should be kept in mind as you read the below
@@ -38,10 +38,10 @@ This program translates lambda expressions into combinator
expressions. But you do not need to know Lambda Calculus to be
impressed by this program!
See the file [fanf.lambda](fanf.lambda) for more examples of lambda calculus
See the file [fanf.lambda](%%REPO_URL%%/1998/fanf/fanf.lambda) for more examples of lambda calculus
source.
Notice how large the code grows from the [fanf.c](fanf.c) into the final
Notice how large the code grows from the [fanf.c](%%REPO_URL%%/1998/fanf/fanf.c) into the final
`fanftmp2.c` C program. Take a look at that final C program again,
can you begin to understand what it is doing?
1998/fanf/index.html
+3 -3
View File
@@ -163,7 +163,7 @@ this entry because of the system resources it requires.</p>
<pre><code> ./try.sh</code></pre>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<h3 id="historical-aside">Historical aside:</h3>
<p>At a time the code in <a href="fanf.c">fanf.c</a> was that of <a href="fanf.orig.c">fanf.orig.c</a>
<p>At a time the code in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/fanf/fanf.c">fanf.c</a> was that of <a href="fanf.orig.c">fanf.orig.c</a>
but to get this to compile in modern systems it had to be translated to what you
now see. The intermediate steps can still be performed but they might be
different from the past. This should be kept in mind as you read the below
@@ -171,9 +171,9 @@ remarks.</p>
<p>This program translates lambda expressions into combinator
expressions. But you do not need to know Lambda Calculus to be
impressed by this program!</p>
<p>See the file <a href="fanf.lambda">fanf.lambda</a> for more examples of lambda calculus
<p>See the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/fanf/fanf.lambda">fanf.lambda</a> for more examples of lambda calculus
source.</p>
<p>Notice how large the code grows from the <a href="fanf.c">fanf.c</a> into the final
<p>Notice how large the code grows from the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/fanf/fanf.c">fanf.c</a> into the final
<code>fanftmp2.c</code> C program. Take a look at that final C program again,
can you begin to understand what it is doing?</p>
<p>Look at the first stage of the C pre-processing which was done like:</p>
1998/schweikh1/README.md
+1 -1
View File
@@ -109,7 +109,7 @@ itself. Just load it in your favorite editor.
`gcc` (the GNU C compiler) must be available at runtime. It is assumed that your
C implementation keeps headers as files in the `/usr/include` directory. The
[info](info) file must be readable and reside in the current working directory.
[info](%%REPO_URL%%/1998/schweikh1/info) file must be readable and reside in the current working directory.
The current working directory must be writable in order to create a temporary
file (which is removed upon program termination). In case you don't have gcc at
runtime, not all is lost if your compiler or preprocessor can produce a list of
1998/schweikh1/index.html
+1 -1
View File
@@ -219,7 +219,7 @@ itself. Just load it in your favorite editor.</p>
<h3 id="requirements">Requirements</h3>
<p><code>gcc</code> (the GNU C compiler) must be available at runtime. It is assumed that your
C implementation keeps headers as files in the <code>/usr/include</code> directory. The
<a href="info">info</a> file must be readable and reside in the current working directory.
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/schweikh1/info">info</a> file must be readable and reside in the current working directory.
The current working directory must be writable in order to create a temporary
file (which is removed upon program termination). In case you don’t have gcc at
runtime, not all is lost if your compiler or preprocessor can produce a list of
1998/schweikh3/README.md
+1 -1
View File
@@ -81,7 +81,7 @@ Thank God the IEEE does not standardize a coding style...
### What this program does
This is best explained in the man page. The troff source for this
man page can be found in the file [samefile.1](samefile.1). To render try:
man page can be found in the file [samefile.1](%%REPO_URL%%/1998/schweikh3/samefile.1). To render try:
``` <!---sh-->
`man ./samefile.1
1998/schweikh3/index.html
+1 -1
View File
@@ -192,7 +192,7 @@ the tool as well at <a href="http://www.schweikhardt.net/samefile" class="uri">h
Thank God the IEEE does not standardize a coding style…</p>
<h3 id="what-this-program-does">What this program does</h3>
<p>This is best explained in the man page. The troff source for this
man page can be found in the file <a href="samefile.1">samefile.1</a>. To render try:</p>
man page can be found in the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/schweikh3/samefile.1">samefile.1</a>. To render try:</p>
<pre><code> `man ./samefile.1</code></pre>
<p>Otherwise:</p>
<h3 id="samefile1-user-manuals-samefile1">SAMEFILE(1) User Manuals SAMEFILE(1)</h3>