Make ^NOTE in markdown/html files bold

This commit is contained in:
Cody Boone Ferguson committed 2024-10-09 11:44:13 -07:00
1 parent cbf87ab40d
commit 9d021fc0b9
174 files changed
+264 -264

No files matched your search

+1 -1
View File
@@ -29,7 +29,7 @@ as the alternate code. See below for the tattoo side-by-side with the code.
### Alternate use:
NOTE: this version might not work on some systems like macOS.
**NOTE**: this version might not work on some systems like macOS.
``` <!---sh-->
./anonymous.alt
+1 -1
View File
@@ -420,7 +420,7 @@ as the alternate code. See below for the tattoo side-by-side with the code.</p>
<h3 id="alternate-build">Alternate build:</h3>
<pre><code> make alt</code></pre>
<h3 id="alternate-use">Alternate use:</h3>
<p>NOTE: this version might not work on some systems like macOS.</p>
<p><strong>NOTE</strong>: this version might not work on some systems like macOS.</p>
<pre><code> ./anonymous.alt</code></pre>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>The author was too embarrassed that they could write such trash, so I
+1 -1
View File
@@ -4,7 +4,7 @@
make all
```
NOTE: there is an [alternate version](#alternate-code) which will only work if
**NOTE**: there is an [alternate version](#alternate-code) which will only work if
you have an old enough compiler or a compiler that supports `-traditional-cpp`.
The original code was fixed in 2023 to not require this.
+1 -1
View File
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<!-- BEFORE: 1st line of markdown file: 1984/decot/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>NOTE: there is an <a href="#alternate-code">alternate version</a> which will only work if
<p><strong>NOTE</strong>: there is an <a href="#alternate-code">alternate version</a> which will only work if
you have an old enough compiler or a compiler that supports <code>-traditional-cpp</code>.
The original code was fixed in 2023 to not require this.</p>
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
+2 -2
View File
@@ -4,7 +4,7 @@
make alt
```
NOTE: the original code will not work on any system other than
**NOTE**: the original code will not work on any system other than
[VAX-11](https://en.wikipedia.org/wiki/VAX-11) and
[PDP-11](https://en.wikipedia.org/wiki/PDP-11) and this is why we encourage you
to use the alt version instead. See [original code](#original-code) below for
@@ -151,7 +151,7 @@ Repo](https://github.com/dspinellis/unix-history-repo/tree/Research-Release).
./gentab gentab > g.c
```
NOTE: it is highly unlikely that you will be able to run the output of `gentab`
**NOTE**: it is highly unlikely that you will be able to run the output of `gentab`
but it should at least compile.
+2 -2
View File
@@ -415,7 +415,7 @@ Location: <a href="../../location.html#NL">NL</a> - <em>Kingdom of the Netherlan
<!-- BEFORE: 1st line of markdown file: 1984/mullender/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make alt</code></pre>
<p>NOTE: the original code will not work on any system other than
<p><strong>NOTE</strong>: the original code will not work on any system other than
<a href="https://en.wikipedia.org/wiki/VAX-11">VAX-11</a> and
<a href="https://en.wikipedia.org/wiki/PDP-11">PDP-11</a> and this is why we encourage you
to use the alt version instead. See <a href="#original-code">original code</a> below for
@@ -502,7 +502,7 @@ Repo</a>.</p>
<pre><code> ./gentab file</code></pre>
<h3 id="gentab-try">gentab try:</h3>
<pre><code> ./gentab gentab &gt; g.c</code></pre>
<p>NOTE: it is highly unlikely that you will be able to run the output of <code>gentab</code>
<p><strong>NOTE</strong>: it is highly unlikely that you will be able to run the output of <code>gentab</code>
but it should at least compile.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="notes-from-the-judges">Notes from the judges:</h3>
+1 -1
View File
@@ -4,7 +4,7 @@
make all
```
NOTE: we **FORCE** disable the optimiser due to a funny problem with different
**NOTE**: we **FORCE** disable the optimiser due to a funny problem with different
compilers and systems. See below and [compilers.html](compilers.html) for details.
There is an [alternate version](#alternate-code). The reason is a funny problem:
+1 -1
View File
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<!-- BEFORE: 1st line of markdown file: 1986/marshall/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>NOTE: we <strong>FORCE</strong> disable the optimiser due to a funny problem with different
<p><strong>NOTE</strong>: we <strong>FORCE</strong> disable the optimiser due to a funny problem with different
compilers and systems. See below and <a href="compilers.html">compilers.html</a> for details.</p>
<p>There is an <a href="#alternate-code">alternate version</a>. The reason is a funny problem:
in modern systems, depending on the platform, compiler and the optimiser, it
+1 -1
View File
@@ -21,7 +21,7 @@
## Judges' remarks:
NOTE: to avoid problems with news and mail, the single line was split
**NOTE**: to avoid problems with news and mail, the single line was split
into 3 lines. Join all lines into a single line to recreate
the original file.
+1 -1
View File
@@ -415,7 +415,7 @@ Location: <a href="../../location.html#ZZ">ZZ</a> - <em>Unknown location</em></l
<h2 id="try">Try:</h2>
<pre><code> ./stein.sh</code></pre>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>NOTE: to avoid problems with news and mail, the single line was split
<p><strong>NOTE</strong>: to avoid problems with news and mail, the single line was split
into 3 lines. Join all lines into a single line to recreate
the original file.</p>
<p>The <code>\015</code> in the above <code>printf(1)</code> command produces a control-N.</p>
+1 -1
View File
@@ -36,7 +36,7 @@ One vendor's lint got hung in an infinite loop over this entry!
FYI: We will let Mark get away with this truly sick entry this time, but
for the future on we have placed a limit on the size of a compile line.
NOTE: originally we made a comment in [Larry Wall](../../authors.html#Larry_Wall)'s
**NOTE**: originally we made a comment in [Larry Wall](../../authors.html#Larry_Wall)'s
[1987/wall](../wall/index.html) entry regarding Mark's contribution but it seems to have
been lost in time. If anyone knows about its whereabouts we'd appreciate letting
us know. Thanks!
+1 -1
View File
@@ -426,7 +426,7 @@ so what if the Makefiles grow a little! :-)</p>
<p>One vendor’s lint got hung in an infinite loop over this entry!</p>
<p>FYI: We will let Mark get away with this truly sick entry this time, but
for the future on we have placed a limit on the size of a compile line.</p>
<p>NOTE: originally we made a comment in <a href="../../authors.html#Larry_Wall">Larry Wall</a>’s
<p><strong>NOTE</strong>: originally we made a comment in <a href="../../authors.html#Larry_Wall">Larry Wall</a>’s
<a href="../wall/index.html">1987/wall</a> entry regarding Mark’s contribution but it seems to have
been lost in time. If anyone knows about its whereabouts we’d appreciate letting
us know. Thanks!</p>
+1 -1
View File
@@ -39,7 +39,7 @@ This entry has a very twisted flow of control via recursion, iteration
and multi-processing. Try to understand what is being done with the
system calls.
NOTE: This program assumes the ASCII character set is being used.
**NOTE**: This program assumes the ASCII character set is being used.
## Author's remarks:
+1 -1
View File
@@ -429,7 +429,7 @@ desired behaviour?</p>
<p>This entry has a very twisted flow of control via recursion, iteration
and multi-processing. Try to understand what is being done with the
system calls.</p>
<p>NOTE: This program assumes the ASCII character set is being used.</p>
<p><strong>NOTE</strong>: This program assumes the ASCII character set is being used.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>No remarks were provided by the author.</p>
<!--
+3 -3
View File
@@ -57,16 +57,16 @@ an EBCDIC machine.
### Historical notes about the original entry
NOTE: If you named the file anything other than `isaak.c`, you had to
**NOTE**: If you named the file anything other than `isaak.c`, you had to
change the `#include` on line 6. This limitation has been fixed in
[isaak.c](%%REPO_URL%%/1988/isaak/isaak.c) and
[isaak.alt.c](%%REPO_URL%%/1988/isaak/isaak.alt.c) by using the `__FILE__` macro.
NOTE: The use of null comments to separate macros to construct different tokens
**NOTE**: The use of null comments to separate macros to construct different tokens
from a single macro (e.g., `"O/**/O"` creates either `++` or `--` by defining
`O` to be `+` or `-`) may cause some strict ANSI C preprocessors to object.
NOTE: Most System V machines were not be able to execute this program correctly
**NOTE**: Most System V machines were not be able to execute this program correctly
due to the fact that BSD style systems have an `sprintf(3)` that returns a `char
*`. Due to the above problems, we placed the output of this program in the
file [isaak.output.txt](isaak.output.txt). Since this was fixed, this file is
+3 -3
View File
@@ -435,14 +435,14 @@ able to compile it.</p>
<p>The program relies heavily on ASCII. Don’t even think of running it on
an EBCDIC machine.</p>
<h3 id="historical-notes-about-the-original-entry">Historical notes about the original entry</h3>
<p>NOTE: If you named the file anything other than <code>isaak.c</code>, you had to
<p><strong>NOTE</strong>: If you named the file anything other than <code>isaak.c</code>, you had to
change the <code>#include</code> on line 6. This limitation has been fixed in
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/isaak/isaak.c">isaak.c</a> and
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/isaak/isaak.alt.c">isaak.alt.c</a> by using the <code>__FILE__</code> macro.</p>
<p>NOTE: The use of null comments to separate macros to construct different tokens
<p><strong>NOTE</strong>: The use of null comments to separate macros to construct different tokens
from a single macro (e.g., <code>"O/**/O"</code> creates either <code>++</code> or <code>--</code> by defining
<code>O</code> to be <code>+</code> or <code>-</code>) may cause some strict ANSI C preprocessors to object.</p>
<p>NOTE: Most System V machines were not be able to execute this program correctly
<p><strong>NOTE</strong>: Most System V machines were not be able to execute this program correctly
due to the fact that BSD style systems have an <code>sprintf(3)</code> that returns a <code>char *</code>. Due to the above problems, we placed the output of this program in the
file <a href="isaak.output.txt">isaak.output.txt</a>. Since this was fixed, this file is
not strictly necessary, but we keep it for historical purposes (decoded as it
+1 -1
View File
@@ -4,7 +4,7 @@
make all
```
NOTE: this version is a fixed version for modern C compilers. See the [Alternate
**NOTE**: this version is a fixed version for modern C compilers. See the [Alternate
code](#alternate-code) section below for how to use the original and why one
might wish to do so.
+1 -1
View File
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<!-- BEFORE: 1st line of markdown file: 1988/westley/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>NOTE: this version is a fixed version for modern C compilers. See the <a href="#alternate-code">Alternate
<p><strong>NOTE</strong>: this version is a fixed version for modern C compilers. See the <a href="#alternate-code">Alternate
code</a> section below for how to use the original and why one
might wish to do so.</p>
<h2 id="try">Try:</h2>
+1 -1
View File
@@ -40,7 +40,7 @@ bugs.html](../../bugs.html#1989_fubar) file). This is, however, a feature, not a
The blank line at the beginning of the source is mandatory.
Do you know why?
NOTE: the file `ouroboros.c` is created by the program itself so this is why it
**NOTE**: the file `ouroboros.c` is created by the program itself so this is why it
is not in the repository.
+1 -1
View File
@@ -429,7 +429,7 @@ loop and compilation error as described in the <a href="../../bugs.html#1989_fub
bugs.html</a> file). This is, however, a feature, not a bug.</p>
<p>The blank line at the beginning of the source is mandatory.
Do you know why?</p>
<p>NOTE: the file <code>ouroboros.c</code> is created by the program itself so this is why it
<p><strong>NOTE</strong>: the file <code>ouroboros.c</code> is created by the program itself so this is why it
is not in the repository.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>In a nutshell, this is probably the slowest and most
+2 -2
View File
@@ -1,6 +1,6 @@
## To build:
NOTE: this will run the program itself.
**NOTE**: this will run the program itself.
``` <!---sh-->
make clobber all
@@ -24,7 +24,7 @@ This alternate code, which prints something slightly different, is provided as w
### Alternate build:
NOTE: this will run the program itself.
**NOTE**: this will run the program itself.
``` <!---sh-->
make clobber alt
+2 -2
View File
@@ -409,7 +409,7 @@ Location: <a href="../../location.html#SE">SE</a> - <em>Kingdom of Sweden</em> (
<!-- BEFORE: 1st line of markdown file: 1989/jar.1/README.md -->
<h2 id="to-build">To build:</h2>
<p>NOTE: this will run the program itself.</p>
<p><strong>NOTE</strong>: this will run the program itself.</p>
<pre><code> make clobber all</code></pre>
<p>There is an alternate version with a slight difference that you may wish to try.
See the <a href="#alternate-code">Alternate code</a> section below for more details.</p>
@@ -418,7 +418,7 @@ See the <a href="#alternate-code">Alternate code</a> section below for more deta
<h2 id="alternate-code">Alternate code:</h2>
<p>This alternate code, which prints something slightly different, is provided as well.</p>
<h3 id="alternate-build">Alternate build:</h3>
<p>NOTE: this will run the program itself.</p>
<p><strong>NOTE</strong>: this will run the program itself.</p>
<pre><code> make clobber alt</code></pre>
<h3 id="alternate-use">Alternate use:</h3>
<pre><code> ./jar.1.alt</code></pre>
+1 -1
View File
@@ -14,7 +14,7 @@
./jar.2 < some_lisp_file
```
NOTE: this entry will likely segfault on invalid input.
**NOTE**: this entry will likely segfault on invalid input.
## Try:
+1 -1
View File
@@ -423,7 +423,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
[enter some lisp]
./jar.2 &lt; some_lisp_file</code></pre>
<p>NOTE: this entry will likely segfault on invalid input.</p>
<p><strong>NOTE</strong>: this entry will likely segfault on invalid input.</p>
<h2 id="try">Try:</h2>
<pre><code> ./try.sh
+1 -1
View File
@@ -60,7 +60,7 @@ value that's not a number.
P=5 ./try.alt.sh
```
NOTE: if you specify too high a value for `P` the program might fail. If you
**NOTE**: if you specify too high a value for `P` the program might fail. If you
specify a value < 0 it will fail to compile.
+1 -1
View File
@@ -434,7 +434,7 @@ value that’s not a number.</p>
<pre><code> ./try.alt.sh
P=5 ./try.alt.sh</code></pre>
<p>NOTE: if you specify too high a value for <code>P</code> the program might fail. If you
<p><strong>NOTE</strong>: if you specify too high a value for <code>P</code> the program might fail. If you
specify a value &lt; 0 it will fail to compile.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>Run this program using your favorite text file as input. Files
+1 -1
View File
@@ -34,7 +34,7 @@ For more detailed information see [1989/robison in bugs.html](../../bugs.html#19
echo 100 / 100 | ./robison # <-- what happens here ?
```
NOTE: This program will very likely crash or break into tiny bits :-) if you
**NOTE**: This program will very likely crash or break into tiny bits :-) if you
feed it numbers with non-binary digits. This, as you might notice if you try one
of the above commands, can happen with other input as well. If you wish to
understand why this happens check the source code.
+1 -1
View File
@@ -427,7 +427,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
./try.sh
echo 100 / 100 | ./robison # &lt;-- what happens here ?</code></pre>
<p>NOTE: This program will very likely crash or break into tiny bits :-) if you
<p><strong>NOTE</strong>: This program will very likely crash or break into tiny bits :-) if you
feed it numbers with non-binary digits. This, as you might notice if you try one
of the above commands, can happen with other input as well. If you wish to
understand why this happens check the source code.</p>
+3 -3
View File
@@ -30,7 +30,7 @@ vim:
- space - pause (space)
- q - quit (:q)
NOTE: after the game ends a file called `HI` will be in the directory with the
**NOTE**: after the game ends a file called `HI` will be in the directory with the
high scores (up to 20 runs saved) so one can see who has the highest score. The
file might look like:
@@ -62,7 +62,7 @@ the judges' additional remarks in the author's remarks, for more details.
Use `tromp.alt` as you would `tromp` above.
NOTE: testing more than one user updating the high score file, one of the
**NOTE**: testing more than one user updating the high score file, one of the
benefits of the alt version, has not been done.
The original unmodified alternate code, which will no longer work right if it
@@ -159,7 +159,7 @@ the `kill -9` command.
"%4d from level %1d by %s\n",w,l,getlogin());pclose(d);}
```
NOTE: the alternate version was fixed for modern systems in 2023.
**NOTE**: the alternate version was fixed for modern systems in 2023.
<!--
+3 -3
View File
@@ -426,7 +426,7 @@ vim:</p>
<li>space - pause (space)</li>
<li>q - quit (:q)</li>
</ul>
<p>NOTE: after the game ends a file called <code>HI</code> will be in the directory with the
<p><strong>NOTE</strong>: after the game ends a file called <code>HI</code> will be in the directory with the
high scores (up to 20 runs saved) so one can see who has the highest score. The
file might look like:</p>
<pre><code> 330 by luser
@@ -442,7 +442,7 @@ the judges’ additional remarks in the author’s remarks, for more details.</p
<pre><code> make alt</code></pre>
<h3 id="alternate-use">Alternate use:</h3>
<p>Use <code>tromp.alt</code> as you would <code>tromp</code> above.</p>
<p>NOTE: testing more than one user updating the high score file, one of the
<p><strong>NOTE</strong>: testing more than one user updating the high score file, one of the
benefits of the alt version, has not been done.</p>
<p>The original unmodified alternate code, which will no longer work right if it
even compiles, is provided later in the author’s remarks.</p>
@@ -519,7 +519,7 @@ the <code>kill -9</code> command.</p>
0);while(getchar()-a[4]);puts(&quot;\033[H\033[J\033[7m&quot;);sigsetmask(s);}}d=popen(
&quot;stty -cbreak echo stop \023;sort -mnr -o HI - HI;cat HI&quot;,&quot;w&quot;);fprintf(d,
&quot;%4d from level %1d by %s\n&quot;,w,l,getlogin());pclose(d);}</code></pre>
<p>NOTE: the alternate version was fixed for modern systems in 2023.</p>
<p><strong>NOTE</strong>: the alternate version was fixed for modern systems in 2023.</p>
<!--
Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.
+1 -1
View File
@@ -59,7 +59,7 @@ Use `baruch.alt` as you would `baruch`.
This program reads an integer between 4 and 99 from the `stdin`.
NOTE: The original program did not have a newline at the end of the file. We
**NOTE**: The original program did not have a newline at the end of the file. We
added a final newline to the file to make unpacking easy.
+1 -1
View File
@@ -442,7 +442,7 @@ question. YMMV.</p>
<p>Use <code>baruch.alt</code> as you would <code>baruch</code>.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>This program reads an integer between 4 and 99 from the <code>stdin</code>.</p>
<p>NOTE: The original program did not have a newline at the end of the file. We
<p><strong>NOTE</strong>: The original program did not have a newline at the end of the file. We
added a final newline to the file to make unpacking easy.</p>
<h2 id="authors-remarks">Authors’ remarks:</h2>
<p>The goal of this work was to write a program that solves the classic <a href="https://en.wikipedia.org/wiki/Eight_queens_puzzle">n-queens
+1 -1
View File
@@ -21,7 +21,7 @@ Give the following lines as input:
RUN
```
NOTE: this entry is probably one of the only times CAPS LOCK might be worth
**NOTE**: this entry is probably one of the only times CAPS LOCK might be worth
having (though still not useful enough to enable :-) ) as all input has to be
UPPER CASE.
+1 -1
View File
@@ -416,7 +416,7 @@ Location: <a href="../../location.html#GR">GR</a> - <em>Hellenic Republic</em> (
<p>Give the following lines as input:</p>
<pre><code> OLD LANDER.BAS
RUN</code></pre>
<p>NOTE: this entry is probably one of the only times CAPS LOCK might be worth
<p><strong>NOTE</strong>: this entry is probably one of the only times CAPS LOCK might be worth
having (though still not useful enough to enable :-) ) as all input has to be
UPPER CASE.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
+1 -1
View File
@@ -63,7 +63,7 @@ even if the receiver lacks `uncompress` and `btoa`:
cmp ../README.md README.md
```
NOTE: a limitation is that the script should be in the parent directory of the
**NOTE**: a limitation is that the script should be in the parent directory of the
directory it is run from.
+1 -1
View File
@@ -449,7 +449,7 @@ even if the receiver lacks <code>uncompress</code> and <code>btoa</code>:</p>
sh ../receive
cmp ../jaw.c jaw.c
cmp ../README.md README.md</code></pre>
<p>NOTE: a limitation is that the script should be in the parent directory of the
<p><strong>NOTE</strong>: a limitation is that the script should be in the parent directory of the
directory it is run from.</p>
<h2 id="authors-remarks">Authors’ remarks:</h2>
<h3 id="abstract">ABSTRACT</h3>
+1 -1
View File
@@ -28,7 +28,7 @@ Note that some compilers will be unable to compile the expression `X=g()...` in
if this is a problem, which is what this alternate code is.
NOTE: it prints something else and it is what the author suggested one try as
**NOTE**: it prints something else and it is what the author suggested one try as
well.
+1 -1
View File
@@ -421,7 +421,7 @@ that can be used if your compiler is incapable of compiling <code>X=g()...</code
<code>main()</code> with:</p>
<pre><code> main(){X=s().v().o().o().l().S().d().l().i().o().w().N();}</code></pre>
<p>if this is a problem, which is what this alternate code is.</p>
<p>NOTE: it prints something else and it is what the author suggested one try as
<p><strong>NOTE</strong>: it prints something else and it is what the author suggested one try as
well.</p>
<h3 id="alternate-build">Alternate build:</h3>
<pre><code> make alt</code></pre>
+2 -2
View File
@@ -43,9 +43,9 @@ below, in the [alternate version](#alternate-code) section.
$ enter some shell commands
```
NOTE: globs do not work with this entry. Why?
**NOTE**: globs do not work with this entry. Why?
NOTE: `exit` does not work and neither does `logout`. To exit try sending ctrl-d
**NOTE**: `exit` does not work and neither does `logout`. To exit try sending ctrl-d
or ctrl-c (or kill it from another terminal :-) ). But why does it not work with
just `exit` or `logout`? Hint: see the authors' remarks.
+2 -2
View File
@@ -437,8 +437,8 @@ below, in the <a href="#alternate-code">alternate version</a> section.</p>
<h2 id="to-use">To use:</h2>
<pre><code> ./tbr
$ enter some shell commands</code></pre>
<p>NOTE: globs do not work with this entry. Why?</p>
<p>NOTE: <code>exit</code> does not work and neither does <code>logout</code>. To exit try sending ctrl-d
<p><strong>NOTE</strong>: globs do not work with this entry. Why?</p>
<p><strong>NOTE</strong>: <code>exit</code> does not work and neither does <code>logout</code>. To exit try sending ctrl-d
or ctrl-c (or kill it from another terminal :-) ). But why does it not work with
just <code>exit</code> or <code>logout</code>? Hint: see the authors’ remarks.</p>
<h2 id="try">Try:</h2>
+1 -1
View File
@@ -99,7 +99,7 @@ the author provides a Fibonacci sequence generator! Try:
./fibonacci 2 1
```
NOTE: if the two args passed to `fibonacci` and `theorem_bkp` add to 0 it will
**NOTE**: if the two args passed to `fibonacci` and `theorem_bkp` add to 0 it will
print 0 over and over again in an infinite loop. In this case it should not be
fixed (another condition where this occurred was fixed in 2023 as it affected
usability of the program).
+1 -1
View File
@@ -459,7 +459,7 @@ the author provides a Fibonacci sequence generator! Try:</p>
make fibonacci
./fibonacci 1 1
./fibonacci 2 1</code></pre>
<p>NOTE: if the two args passed to <code>fibonacci</code> and <code>theorem_bkp</code> add to 0 it will
<p><strong>NOTE</strong>: if the two args passed to <code>fibonacci</code> and <code>theorem_bkp</code> add to 0 it will
print 0 over and over again in an infinite loop. In this case it should not be
fixed (another condition where this occurred was fixed in 2023 as it affected
usability of the program).</p>
+2 -2
View File
@@ -15,7 +15,7 @@ code](#alternate-code) below.
./ant some_file
```
NOTE: the file must already exist and not specifying any arg will make the
**NOTE**: the file must already exist and not specifying any arg will make the
program exit without doing anything.
@@ -74,7 +74,7 @@ problem if you ARE a vi(m) user! :-) ... especially if you don't read the
information below. This means if you're reading this in vi(m) you'll have to
exit this like in normal vi(m) and then try the same with `./ant` only to fail. :-)
NOTE: to enter form feed you should be able to hit `ctrl-L`. This will allow you
**NOTE**: to enter form feed you should be able to hit `ctrl-L`. This will allow you
to exit insert mode rather than ESC like in normal vi(m). See the author's
commands section for other commands.
+2 -2
View File
@@ -415,7 +415,7 @@ that might feel a bit more familiar to vi(m) users. See <a href="#alternate-code
code</a> below.</p>
<h2 id="to-use">To use:</h2>
<pre><code> ./ant some_file</code></pre>
<p>NOTE: the file must already exist and not specifying any arg will make the
<p><strong>NOTE</strong>: the file must already exist and not specifying any arg will make the
program exit without doing anything.</p>
<h2 id="try">Try:</h2>
<pre><code> make hill
@@ -449,7 +449,7 @@ insert mode) and ask them to exit. Well in this case you’re likely to have thi
problem if you ARE a vi(m) user! :-) … especially if you don’t read the
information below. This means if you’re reading this in vi(m) you’ll have to
exit this like in normal vi(m) and then try the same with <code>./ant</code> only to fail. :-)</p>
<p>NOTE: to enter form feed you should be able to hit <code>ctrl-L</code>. This will allow you
<p><strong>NOTE</strong>: to enter form feed you should be able to hit <code>ctrl-L</code>. This will allow you
to exit insert mode rather than ESC like in normal vi(m). See the author’s
commands section for other commands.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
+1 -1
View File
@@ -23,7 +23,7 @@ the source code. The judges were unmoved by this blatant attempt to influence
the contest and rejected this idea... so we gave it the "Best of Show"
instead!!
NOTE: One should remove the final trailing newline to obtain the
**NOTE**: One should remove the final trailing newline to obtain the
original source file. This step is not needed to compile
this entry.
+1 -1
View File
@@ -420,7 +420,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
the source code. The judges were unmoved by this blatant attempt to influence
the contest and rejected this idea… so we gave it the “Best of Show”
instead!!</p>
<p>NOTE: One should remove the final trailing newline to obtain the
<p><strong>NOTE</strong>: One should remove the final trailing newline to obtain the
original source file. This step is not needed to compile
this entry.</p>
<p>To have a chance to compile under a modern CPP, we had to
+1 -1
View File
@@ -23,7 +23,7 @@ Why is the following label necessary?
Notice that if you C beautify (cb) or pre-process this program, it
will no longer work correctly, if at all. Go ahead, try it... :-)
NOTE: One should remove the final trailing newline to obtain the
**NOTE**: One should remove the final trailing newline to obtain the
original source file. This step is not needed to compile
this entry.
+1 -1
View File
@@ -417,7 +417,7 @@ Location: <a href="../../location.html#FR">FR</a> - <em>French Republic</em> (<e
<pre><code> sorryfor_this_unused_but_very_needed_label:</code></pre>
<p>Notice that if you C beautify (cb) or pre-process this program, it
will no longer work correctly, if at all. Go ahead, try it… :-)</p>
<p>NOTE: One should remove the final trailing newline to obtain the
<p><strong>NOTE</strong>: One should remove the final trailing newline to obtain the
original source file. This step is not needed to compile
this entry.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
+1 -1
View File
@@ -61,7 +61,7 @@ that the program works even when the server and the client have
different architectures). It buffers communication to the X
server for efficiency.
NOTE: The original source in davidguy.c used only an IP address
**NOTE**: The original source in davidguy.c used only an IP address
argument (assumed :0.0) and assumed the color of black
and white.
+1 -1
View File
@@ -443,7 +443,7 @@ performs whatever byte-swapping and bit-reversal is needed (so
that the program works even when the server and the client have
different architectures). It buffers communication to the X
server for efficiency.</p>
<p>NOTE: The original source in davidguy.c used only an IP address
<p><strong>NOTE</strong>: The original source in davidguy.c used only an IP address
argument (assumed :0.0) and assumed the color of black
and white.</p>
<p>The program doesn’t require any user interaction; you can just sit
+1 -1
View File
@@ -59,7 +59,7 @@ The author wishes to thank J Greely for the last 6 bytes.
Here's about how it does it:
NOTE: Bits are referred to as 76543210, high to low.
**NOTE**: Bits are referred to as 76543210, high to low.
1. Get the character in variable `a`. Note the fun way we check for `EOF`.
(thanks J).
+1 -1
View File
@@ -441,7 +441,7 @@ and information.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>The author wishes to thank J Greely for the last 6 bytes.</p>
<p>Here’s about how it does it:</p>
<p>NOTE: Bits are referred to as 76543210, high to low.</p>
<p><strong>NOTE</strong>: Bits are referred to as 76543210, high to low.</p>
<ol type="1">
<li><p>Get the character in variable <code>a</code>. Note the fun way we check for <code>EOF</code>.
(thanks J).</p></li>
+1 -1
View File
@@ -19,7 +19,7 @@ For more detailed information see [1991/westley in bugs.html](../../bugs.html#19
## To use:
NOTE: we have provided a script to perform the below procedure which we include
**NOTE**: we have provided a script to perform the below procedure which we include
for the interested. See the [try](#try) section if you just want to play.
Make and then run as follows:
+1 -1
View File
@@ -419,7 +419,7 @@ time.</p>
</blockquote>
<p>For more detailed information see <a href="../../bugs.html#1991_westley">1991/westley in bugs.html</a>.</p>
<h2 id="to-use">To use:</h2>
<p>NOTE: we have provided a script to perform the below procedure which we include
<p><strong>NOTE</strong>: we have provided a script to perform the below procedure which we include
for the interested. See the <a href="#try">try</a> section if you just want to play.</p>
<p>Make and then run as follows:</p>
<pre><code> ./westley [move_location] | tee nextmove.c</code></pre>
+1 -1
View File
@@ -32,7 +32,7 @@ For the slow minded, try:
Once you get past the obfuscation, you have an opportunity to learn
about regular expressions and state machines.
NOTE: Some compilers have had trouble optimizing this entry.
**NOTE**: Some compilers have had trouble optimizing this entry.
## Author's remarks:
+1 -1
View File
@@ -423,7 +423,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>Once you get past the obfuscation, you have an opportunity to learn
about regular expressions and state machines.</p>
<p>NOTE: Some compilers have had trouble optimizing this entry.</p>
<p><strong>NOTE</strong>: Some compilers have had trouble optimizing this entry.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="adrians-grep-adgrep">ADrian’s GREP (adgrep)</h3>
<p>For those confused by the complexity of full-blown <code>egrep(1)</code> style regular
+1 -1
View File
@@ -32,7 +32,7 @@ output.
Of course, the source (layout) is self-documenting! :-)
NOTE: The original winning source assumed that `exit(3)` returned a value which
**NOTE**: The original winning source assumed that `exit(3)` returned a value which
cause problems for some systems where `exit(3)` returns a void. The file
[imc.c](%%REPO_URL%%/1992/imc/imc.c) has been modified to avoid this problem. The original file also
declared argc to be a `long` which was fixed.
+1 -1
View File
@@ -423,7 +423,7 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
Sun raster file. Others can make use of the <code>-text</code> flag for character oriented
output.</p>
<p>Of course, the source (layout) is self-documenting! :-)</p>
<p>NOTE: The original winning source assumed that <code>exit(3)</code> returned a value which
<p><strong>NOTE</strong>: The original winning source assumed that <code>exit(3)</code> returned a value which
cause problems for some systems where <code>exit(3)</code> returns a void. The file
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/imc.c">imc.c</a> has been modified to avoid this problem. The original file also
declared argc to be a <code>long</code> which was fixed.</p>
+3 -3
View File
@@ -6,7 +6,7 @@ If your machine support the X Window System, Version 11:
make alt
```
NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
**NOTE**: this entry requires the `X11/Xlib.h` header file and the X11 library to
compile. See the
FAQ on "[X11](../../faq.html#X11)"
if you need help.
@@ -77,10 +77,10 @@ Use `kivinen` as you would `kivinen.alt`.
The type of entertainment depends on number of arguments
you have with the program. :-)
NOTE: Some systems do not need (or have) `-lsocket -lresolv -lnsl`.
**NOTE**: Some systems do not need (or have) `-lsocket -lresolv -lnsl`.
Such systems should compile using `-lX11`.
NOTE: The original winning source [kivinen.orig.c](%%REPO_URL%%/1992/kivinen/kivinen.orig.c) assumed that
**NOTE**: The original winning source [kivinen.orig.c](%%REPO_URL%%/1992/kivinen/kivinen.orig.c) assumed that
`exit(3)` returned a value which cause problems for some systems where `exit(3)` returns
`void`. The file [kivinen.c](%%REPO_URL%%/1992/kivinen/kivinen.c) avoids this problem.
+3 -3
View File
@@ -411,7 +411,7 @@ Location: <a href="../../location.html#FI">FI</a> - <em>Republic of Finland </em
<h2 id="to-build">To build:</h2>
<p>If your machine support the X Window System, Version 11:</p>
<pre><code> make alt</code></pre>
<p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
<p><strong>NOTE</strong>: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
compile. See the
FAQ on “<a href="../../faq.html#X11">X11</a>”
if you need help.</p>
@@ -449,9 +449,9 @@ code.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>The type of entertainment depends on number of arguments
you have with the program. :-)</p>
<p>NOTE: Some systems do not need (or have) <code>-lsocket -lresolv -lnsl</code>.
<p><strong>NOTE</strong>: Some systems do not need (or have) <code>-lsocket -lresolv -lnsl</code>.
Such systems should compile using <code>-lX11</code>.</p>
<p>NOTE: The original winning source <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/kivinen/kivinen.orig.c">kivinen.orig.c</a> assumed that
<p><strong>NOTE</strong>: The original winning source <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/kivinen/kivinen.orig.c">kivinen.orig.c</a> assumed that
<code>exit(3)</code> returned a value which cause problems for some systems where <code>exit(3)</code> returns
<code>void</code>. The file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/kivinen/kivinen.c">kivinen.c</a> avoids this problem.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
+3 -3
View File
@@ -18,11 +18,11 @@ The object is to refill the table with `5`s, by incrementing or decrementing
numbers as needed. It is the side effects that get you into trouble. If you
are not careful, you may find things "at `6`s and `7`s". :-)
NOTE: Some compilers have had trouble optimizing this entry.
**NOTE**: Some compilers have had trouble optimizing this entry.
NOTE: Some systems need to compile with `-ltermcap` as well as `-lcurses`.
**NOTE**: Some systems need to compile with `-ltermcap` as well as `-lcurses`.
NOTE: The original winning source
**NOTE**: The original winning source
[marangon.orig.c](%%REPO_URL%%/1992/marangon/marangon.orig.c) assumed that
`exit(3)` returns a value which cause problems for some systems where `exit(3)`
returns a `void`. The file [marangon.c](%%REPO_URL%%/1992/marangon/marangon.c)
+3 -3
View File
@@ -416,9 +416,9 @@ Location: <a href="../../location.html#IT">IT</a> - <em>Italian Republic</em> (<
<p>The object is to refill the table with <code>5</code>s, by incrementing or decrementing
numbers as needed. It is the side effects that get you into trouble. If you
are not careful, you may find things “at <code>6</code>s and <code>7</code>s”. :-)</p>
<p>NOTE: Some compilers have had trouble optimizing this entry.</p>
<p>NOTE: Some systems need to compile with <code>-ltermcap</code> as well as <code>-lcurses</code>.</p>
<p>NOTE: The original winning source
<p><strong>NOTE</strong>: Some compilers have had trouble optimizing this entry.</p>
<p><strong>NOTE</strong>: Some systems need to compile with <code>-ltermcap</code> as well as <code>-lcurses</code>.</p>
<p><strong>NOTE</strong>: The original winning source
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/marangon/marangon.orig.c">marangon.orig.c</a> assumed that
<code>exit(3)</code> returns a value which cause problems for some systems where <code>exit(3)</code>
returns a <code>void</code>. The file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/marangon/marangon.c">marangon.c</a>
+2 -2
View File
@@ -47,9 +47,9 @@ For a real quick game try:
66 46
```
NOTE: Move values must be restricted to the range 00 to 77.
**NOTE**: Move values must be restricted to the range 00 to 77.
NOTE: Because some mailers have problems with the original winning source,
**NOTE**: Because some mailers have problems with the original winning source,
a slightly modified version with shorter lines has been provided.
+2 -2
View File
@@ -432,8 +432,8 @@ suggested above. :-)</p>
65 55
66 46</code></pre>
<p>NOTE: Move values must be restricted to the range 00 to 77.</p>
<p>NOTE: Because some mailers have problems with the original winning source,
<p><strong>NOTE</strong>: Move values must be restricted to the range 00 to 77.</p>
<p><strong>NOTE</strong>: Because some mailers have problems with the original winning source,
a slightly modified version with shorter lines has been provided.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>This program plays chess. You play the white pieces and the program the black
+2 -2
View File
@@ -9,7 +9,7 @@ section below to run the original (the bug also exists here).
make alt
```
NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
**NOTE**: this entry requires the `X11/Xlib.h` header file and the X11 library to
compile. For more information see the
FAQ on "[X11](../../faq.html#X11)".
@@ -42,7 +42,7 @@ where:
`speed` is update speed from 1 to 9 (default is 9).
NOTE: in most cases `DISPLAY` should already be set.
**NOTE**: in most cases `DISPLAY` should already be set.
## Original code:
+2 -2
View File
@@ -414,7 +414,7 @@ this entry was like back in 1993 (though see the <a href="../../bugs.html#1993_c
bugs.html</a>). See the <a href="#original-code">original code</a>
section below to run the original (the bug also exists here).</p>
<pre><code> make alt</code></pre>
<p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
<p><strong>NOTE</strong>: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
compile. For more information see the
FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
<p>To configure how many microseconds to sleep before updates try:</p>
@@ -431,7 +431,7 @@ FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
./cmills.alt [speed] # must be run on an X11 server</code></pre>
<p>where:</p>
<p><code>speed</code> is update speed from 1 to 9 (default is 9).</p>
<p>NOTE: in most cases <code>DISPLAY</code> should already be set.</p>
<p><strong>NOTE</strong>: in most cases <code>DISPLAY</code> should already be set.</p>
<h2 id="original-code">Original code:</h2>
<p>We recommend the version that uses <code>usleep(3)</code> to more easily see what is going
on but you can use the original without any delays if you wish.</p>
+1 -1
View File
@@ -4,7 +4,7 @@
make all
```
NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
**NOTE**: this entry requires the `X11/Xlib.h` header file and the X11 library to
compile. For more information see the
FAQ on "[X11](../../faq.html#X11)".
+1 -1
View File
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#NO">NO</a> - <em>Kingdom of Norway</em> (
<!-- BEFORE: 1st line of markdown file: 1993/jonth/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
<p><strong>NOTE</strong>: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
compile. For more information see the
FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
<h2 id="to-use">To use:</h2>
+1 -1
View File
@@ -18,7 +18,7 @@ traditional fashion of C.
For an explanation of why and how this works see the author's remarks. The gist
of the entry itself, however, is the file name _itself_ **is** _part of the code_.
NOTE: We delete the temporary file as part of `make all` whether
**NOTE**: We delete the temporary file as part of `make all` whether
or not the compilation succeeds. This is a Makefile **feature**
that might **bug** anyone running the make command. :-)
+1 -1
View File
@@ -417,7 +417,7 @@ Location: <a href="../../location.html#FI">FI</a> - <em>Republic of Finland </em
traditional fashion of C.</p>
<p>For an explanation of why and how this works see the author’s remarks. The gist
of the entry itself, however, is the file name <em>itself</em> <strong>is</strong> <em>part of the code</em>.</p>
<p>NOTE: We delete the temporary file as part of <code>make all</code> whether
<p><strong>NOTE</strong>: We delete the temporary file as part of <code>make all</code> whether
or not the compilation succeeds. This is a Makefile <strong>feature</strong>
that might <strong>bug</strong> anyone running the make command. :-)</p>
<p>This entry will not compile with gcc version &gt;= 2.3.3 as it relied
+1 -1
View File
@@ -4,7 +4,7 @@
make all
```
NOTE: there are two alternate versions of this program, both allowing one to
**NOTE**: there are two alternate versions of this program, both allowing one to
slow down the game and the second one with movements more familiar to vi users.
See the [Alternate code](#alternate-code) section below.
+1 -1
View File
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
<!-- BEFORE: 1st line of markdown file: 1993/rince/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>NOTE: there are two alternate versions of this program, both allowing one to
<p><strong>NOTE</strong>: there are two alternate versions of this program, both allowing one to
slow down the game and the second one with movements more familiar to vi users.
See the <a href="#alternate-code">Alternate code</a> section below.</p>
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
+1 -1
View File
@@ -79,7 +79,7 @@ The author suggests the following questions when using
We suggest you try using the body (minus the header and signature line)
of a Usenet article. You might want to try something from _alt.flame_. :-)
NOTE: If you have certain `'` in the question this entry might fail.
**NOTE**: If you have certain `'` in the question this entry might fail.
## Author's remarks:
+1 -1
View File
@@ -453,7 +453,7 @@ some questions related to the text.</p>
</ul>
<p>We suggest you try using the body (minus the header and signature line)
of a Usenet article. You might want to try something from <em>alt.flame</em>. :-)</p>
<p>NOTE: If you have certain <code>'</code> in the question this entry might fail.</p>
<p><strong>NOTE</strong>: If you have certain <code>'</code> in the question this entry might fail.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>I wanted to write a program that would read in a text file in
natural language (such as English) and answer questions about that
+1 -1
View File
@@ -4,7 +4,7 @@
make all
```
NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
**NOTE**: this entry requires the `X11/Xlib.h` header file and the X11 library to
compile. For more information see the
FAQ on "[X11](../../faq.html#X11)".
+1 -1
View File
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#FI">FI</a> - <em>Republic of Finland </em
<!-- BEFORE: 1st line of markdown file: 1994/tvr/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
<p><strong>NOTE</strong>: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
compile. For more information see the
FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
<p>The author provided a less obfuscated version as alternate code. See <a href="#alternate-code">Alternate
+1 -1
View File
@@ -58,7 +58,7 @@ where you get _messages as compiler errors_**. Depending on the compiler line yo
will get different error messages and one compiler line will make you win the
game!
NOTE: your terminal should be set to 80 columns, 8 character tabs, and
**NOTE**: your terminal should be set to 80 columns, 8 character tabs, and
wraparound. The alternate code does not have this limitation and it is for this
reason that we recommend you try it first.
+1 -1
View File
@@ -441,7 +441,7 @@ and then run the program each time. For example:</p>
where you get <em>messages as compiler errors</em></strong>. Depending on the compiler line you
will get different error messages and one compiler line will make you win the
game!</p>
<p>NOTE: your terminal should be set to 80 columns, 8 character tabs, and
<p><strong>NOTE</strong>: your terminal should be set to 80 columns, 8 character tabs, and
wraparound. The alternate code does not have this limitation and it is for this
reason that we recommend you try it first.</p>
<h3 id="original-build">Original build:</h3>
+1 -1
View File
@@ -21,7 +21,7 @@ For more detailed information see [1995/savastio in bugs.html](../../bugs.html#1
# enter a POSITIVE number such as 100
```
NOTE: if you specify a negative number it will get stuck, showing no output. But
**NOTE**: if you specify a negative number it will get stuck, showing no output. But
what happens if you give a non-number?
+1 -1
View File
@@ -419,7 +419,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<h2 id="to-use">To use:</h2>
<pre><code> ./savastio
# enter a POSITIVE number such as 100</code></pre>
<p>NOTE: if you specify a negative number it will get stuck, showing no output. But
<p><strong>NOTE</strong>: if you specify a negative number it will get stuck, showing no output. But
what happens if you give a non-number?</p>
<h2 id="try">Try:</h2>
<pre><code> ./try.sh</code></pre>
+1 -1
View File
@@ -4,7 +4,7 @@
make all
```
NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
**NOTE**: this entry requires the `X11/Xlib.h` header file and the X11 library to
compile. For more information see the
FAQ on "[X11](../../faq.html#X11)".
+1 -1
View File
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<!-- BEFORE: 1st line of markdown file: 1998/banks/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
<p><strong>NOTE</strong>: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
compile. For more information see the
FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
<p>If you do not have a page up or page down key you might wish to see the
+1 -1
View File
@@ -4,7 +4,7 @@
make chaos
```
NOTE: Some systems do not implement `halfdelay()` in their `libcurses`.
**NOTE**: Some systems do not implement `halfdelay()` in their `libcurses`.
You might try compiling with `-lncurses` if you have that library.
Or you can build this entry without the `halfdelay()` call by:
+1 -1
View File
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<!-- BEFORE: 1st line of markdown file: 1998/chaos/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make chaos</code></pre>
<p>NOTE: Some systems do not implement <code>halfdelay()</code> in their <code>libcurses</code>.
<p><strong>NOTE</strong>: Some systems do not implement <code>halfdelay()</code> in their <code>libcurses</code>.
You might try compiling with <code>-lncurses</code> if you have that library.
Or you can build this entry without the <code>halfdelay()</code> call by:</p>
<pre><code> make chaos_nohalf</code></pre>
+1 -1
View File
@@ -4,7 +4,7 @@
make all
```
NOTE: this may take a while. Some systems may have problems building
**NOTE**: this may take a while. Some systems may have problems building
this entry because of the system resources it requires.
+1 -1
View File
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
<!-- BEFORE: 1st line of markdown file: 1998/fanf/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>NOTE: this may take a while. Some systems may have problems building
<p><strong>NOTE</strong>: this may take a while. Some systems may have problems building
this entry because of the system resources it requires.</p>
<h2 id="to-use">To use:</h2>
<pre><code> ./fanf</code></pre>
+1 -1
View File
@@ -46,7 +46,7 @@ Now try running:
And observe that it matches what you had in the previous run!
NOTE: changing the dimension parameters (see the authors' remarks) renders
**NOTE**: changing the dimension parameters (see the authors' remarks) renders
existing spreadsheet files unusable.
+1 -1
View File
@@ -431,7 +431,7 @@ FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
<p>Now try running:</p>
<pre><code> ./jarijyrki &lt; myedits.info</code></pre>
<p>And observe that it matches what you had in the previous run!</p>
<p>NOTE: changing the dimension parameters (see the authors’ remarks) renders
<p><strong>NOTE</strong>: changing the dimension parameters (see the authors’ remarks) renders
existing spreadsheet files unusable.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>This entry is one of those that makes you wonder why some commercial software
+1 -1
View File
@@ -73,7 +73,7 @@ Like with [try.sh](%%REPO_URL%%/2000/natori/try.sh), try using this multiple tim
the day on different days (if different phases of the Moon you'll see more of a
difference, of course).
NOTE: if it's a Full Moon the script won't look as nice.
**NOTE**: if it's a Full Moon the script won't look as nice.
## Judges' remarks:
+1 -1
View File
@@ -442,7 +442,7 @@ versions? Or are there any?</p>
<p>Like with <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/natori/try.sh">try.sh</a>, try using this multiple times in a row or throughout
the day on different days (if different phases of the Moon you’ll see more of a
difference, of course).</p>
<p>NOTE: if it’s a Full Moon the script won’t look as nice.</p>
<p><strong>NOTE</strong>: if it’s a Full Moon the script won’t look as nice.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>Here is a nice compact program that changes with the phase of the Moon.
Can you figure out how it does it?</p>
+1 -1
View File
@@ -20,7 +20,7 @@ For more detailed information see [2000/primenum in bugs.html](../../bugs.html#2
echo n | ./primenum n
```
NOTE: `n` is an integer.
**NOTE**: `n` is an integer.
## Try:
+1 -1
View File
@@ -418,7 +418,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<p>For more detailed information see <a href="../../bugs.html#2000_primenum">2000/primenum in bugs.html</a>.</p>
<h2 id="to-use">To use:</h2>
<pre><code> echo n | ./primenum n</code></pre>
<p>NOTE: <code>n</code> is an integer.</p>
<p><strong>NOTE</strong>: <code>n</code> is an integer.</p>
<h2 id="try">Try:</h2>
<pre><code> ./try.sh</code></pre>
<h2 id="judges-remarks">Judges’ remarks:</h2>
+1 -1
View File
@@ -85,7 +85,7 @@ file and saves it into `test.wav`.
The output format of the program is 8KHz, unsigned 8-bit samples.
NOTE: the program's return code is meaningless.
**NOTE**: the program's return code is meaningless.
### Audio quality
+1 -1
View File
@@ -455,7 +455,7 @@ format, you can pipe it to <a href="https://en.wikipedia.org/wiki/SoX">SoX</a> f
<p>converts the output of the program into a 44.1KHz stereo .WAV
file and saves it into <code>test.wav</code>.</p>
<p>The output format of the program is 8KHz, unsigned 8-bit samples.</p>
<p>NOTE: the program’s return code is meaningless.</p>
<p><strong>NOTE</strong>: the program’s return code is meaningless.</p>
<h3 id="audio-quality">Audio quality</h3>
<p>The quality of the sound produced by the program is cross between a
<a href="https://en.wikipedia.org/wiki/Tin_can_telephone">yogurt-pot-and-string
+1 -1
View File
@@ -21,7 +21,7 @@ For more detailed information see [2001/herrmann1 in bugs.html](../../bugs.html#
./herrmann1.sh 'prg=file'
```
NOTE: this entry seems to rely on older versions of gcc for the compilation
**NOTE**: this entry seems to rely on older versions of gcc for the compilation
stage and as such if you wish to see that part like it was designed you will
need an older compiler perhaps gcc 2.95.
+1 -1
View File
@@ -419,7 +419,7 @@ Location: <a href="../../location.html#DE">DE</a> - <em>Federal Republic of Germ
<p>For more detailed information see <a href="../../bugs.html#2001_herrmann1">2001/herrmann1 in bugs.html</a>.</p>
<h2 id="to-use">To use:</h2>
<pre><code> ./herrmann1.sh &#39;prg=file&#39;</code></pre>
<p>NOTE: this entry seems to rely on older versions of gcc for the compilation
<p><strong>NOTE</strong>: this entry seems to rely on older versions of gcc for the compilation
stage and as such if you wish to see that part like it was designed you will
need an older compiler perhaps gcc 2.95.</p>
<h2 id="try">Try:</h2>
+1 -1
View File
@@ -20,7 +20,7 @@ For more detailed information see [2005/mikeash in bugs.html](../../bugs.html#20
./mikeash
```
NOTE: the author stated that they tested this under i386 machines but this works
**NOTE**: the author stated that they tested this under i386 machines but this works
under 64-bit (x86_64, arm64) machines too.
+1 -1
View File
@@ -418,7 +418,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<p>For more detailed information see <a href="../../bugs.html#2005_mikeash">2005/mikeash in bugs.html</a>.</p>
<h2 id="to-use">To use:</h2>
<pre><code> ./mikeash</code></pre>
<p>NOTE: the author stated that they tested this under i386 machines but this works
<p><strong>NOTE</strong>: the author stated that they tested this under i386 machines but this works
under 64-bit (x86_64, arm64) machines too.</p>
<h2 id="try">Try:</h2>
<pre><code> ./try.sh</code></pre>
+1 -1
View File
@@ -27,7 +27,7 @@ For more detailed information see [2011/fredriksson in bugs.html](../../bugs.htm
./try.sh
```
NOTE: you need to be allowed to change your stack size or else the last command
**NOTE**: you need to be allowed to change your stack size or else the last command
in the script would likely cause the program to dump core, which is why the
script checks the exit code of `ulimit` first.
+1 -1
View File
@@ -420,7 +420,7 @@ Location: <a href="../../location.html#FI">FI</a> - <em>Republic of Finland </em
<pre><code> ./fredriksson [-icvtnk#] regexp &lt; file</code></pre>
<h2 id="try">Try:</h2>
<pre><code> ./try.sh</code></pre>
<p>NOTE: you need to be allowed to change your stack size or else the last command
<p><strong>NOTE</strong>: you need to be allowed to change your stack size or else the last command
in the script would likely cause the program to dump core, which is why the
script checks the exit code of <code>ulimit</code> first.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
Loaded 100 of 174 files, more files were not shown because too many files have changed in this diff. Show more