changes to improve the general format of markdown files

2024-03-20 15:32:31 -07:00
1 parent 6ab0485404
commit dcd33ae8d5
@@ -33,7 +33,6 @@ make clobber alt

 ### Alternate use:

-
 ```sh
 ./jar.1.alt
 ```
@@ -50,6 +50,7 @@ program to fail and a negative value will cause a compilation error.
 ./ovdluhe.alt
 ```

+
 ### Alternate try:

 ```sh
@@ -19,7 +19,6 @@ STATUS: INABIAF - please **DO NOT** fix
 For more detailed information see [1990 baruch bugs](../../bugs.html#1990_baruch).


-
 ## To use:

 ```sh
@@ -40,8 +40,6 @@ y1 - initial value  (y(x1) == y1)
 ```


-
-
 ## Judges' remarks:

 The program's source implements four functions, all from the
@@ -80,6 +80,7 @@ Use `albert.alt` as you would `albert` above.
 ./try.alt.sh
 ```

+
 ## Judges' remarks:

 We were impressed with the speed at which it was able to factor
@@ -18,7 +18,6 @@ where `Makefile` is a Makefile to use and `rule` is an optional rule to use.

 ## Try:

-
 ```sh
 ./try.sh
 ```
@@ -79,6 +79,7 @@ Use `buzzard.2.alt` as you would `buzzard.2` above.
 ./try.alt.sh
 ```

+
 ## Judges' remarks:

 Have fun!
@@ -21,7 +21,6 @@ make clobber SLEEP=200 alt
 ```


-
 ### Bugs and (Mis)features:

 The current status of this entry is:
@@ -20,7 +20,6 @@ level   a value from -128 to 127

 ## Try:

-
 ```sh
 ./try.sh
 ```
@@ -59,7 +59,7 @@ where `altmode` `1` - `4` correspond to mode `0` - `3` in the original entry and
 `altmode 0` calculates Mandelbrot/Julian sets correctly.


-## Alternate try:
+### Alternate try:

 ```sh
 ./try.alt.color.sh			# for colour displays
@@ -161,7 +161,7 @@ code</a> below.</p>
 <div class="sourceCode" id="cb6"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./tvr.alt</span> altmode screensize/2 <span class="op">&lt;</span> colormapfile</span></code></pre></div>
 <p>where <code>altmode</code> <code>1</code> - <code>4</code> correspond to mode <code>0</code> - <code>3</code> in the original entry and
 <code>altmode 0</code> calculates Mandelbrot/Julian sets correctly.</p>
-<h2 id="alternate-try">Alternate try:</h2>
+<h3 id="alternate-try">Alternate try:</h3>
 <div class="sourceCode" id="cb7"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./try.alt.color.sh</span>          <span class="co"># for colour displays</span></span>
 <span id="cb7-2"><a href="#cb7-2" aria-hidden="true" tabindex="-1"></a><span class="ex">./try.alt.bw.sh</span>         <span class="co"># for Black &amp; White displays</span></span></code></pre></div>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
@@ -15,7 +15,6 @@ see [Original code](#original-code) below.

 ## To use:

-
 ```sh
 ./westley.alt
 ```
@@ -35,7 +34,7 @@ get a better idea or see below in the [Try](#try) section for running the game
 from start to finish.


-### Try:
+## Try:

 For something more interesting try compiling it with different `cc -D` arguments
 and then run the program each time.  For example:
@@ -76,7 +75,7 @@ better idea or see below in the [Original try](#original-try) section for
 running the game from start to finish.


-## Original use:
+### Original use:

 There is no running of this program directly as it is supposed to fail to
 compile: the purpose of the game is to escape the dungeon but depending on the
@@ -91,7 +90,7 @@ you do not run this program as it will not compile: instead it will be compiler
 error messages; there is no running the program.


-## Original try:
+### Original try:

 For something more interesting try compiling it with different `cc -D`
 arguments:
@@ -160,7 +160,7 @@ invocations</em> specified. That means with the right compiler invocation you ca
 message you get. You might wish to look at the <a href="westley.alt.c">source code</a> to
 get a better idea or see below in the <a href="#try">Try</a> section for running the game
 from start to finish.</p>
-<h3 id="try">Try:</h3>
+<h2 id="try">Try:</h2>
 <p>For something more interesting try compiling it with different <code>cc -D</code> arguments
 and then run the program each time. For example:</p>
 <div class="sourceCode" id="cb3"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Door</span> westley.alt.c <span class="at">-o</span> westley.alt <span class="kw">&amp;&amp;</span> <span class="ex">./westley.alt</span></span>
@@ -181,7 +181,7 @@ reason that we recommend you try it first.</p>
 message you get. You might wish to look at the <a href="westley.c">source code</a> to get a
 better idea or see below in the <a href="#original-try">Original try</a> section for
 running the game from start to finish.</p>
-<h2 id="original-use">Original use:</h2>
+<h3 id="original-use">Original use:</h3>
 <p>There is no running of this program directly as it is supposed to fail to
 compile: the purpose of the game is to escape the dungeon but depending on the
 compiler line you will get a different message (<strong>as compiler errors</strong> due to
@@ -192,7 +192,7 @@ invocations</em> specified. That means with the right compiler invocation you ca
 ‘win’ the game on the first go. But unlike the <a href="westley.alt.c">alternate code</a>,
 you do not run this program as it will not compile: instead it will be compiler
 error messages; there is no running the program.</p>
-<h2 id="original-try">Original try:</h2>
+<h3 id="original-try">Original try:</h3>
 <p>For something more interesting try compiling it with different <code>cc -D</code>
 arguments:</p>
 <div class="sourceCode" id="cb6"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cc</span> <span class="at">-Describe</span> <span class="at">-Door</span> westley.c</span>
@@ -35,7 +35,6 @@ For more detailed information see [1995 cdua bugs](../../bugs.html#1995_cdua).

 ## Try:

-
 ```sh
 make SLEEP=1500 clobber alt

@@ -16,7 +16,6 @@ STATUS: known bug - please help us fix
 For more detailed information see [1995 leo bugs](../../bugs.html#1995_leo).


-
 ## To use:

 ```sh
@@ -41,7 +41,6 @@ This version is the original which has no sleep time in between updates.

 ### Original build:

-
 ```sh
 make all
 ```
@@ -23,7 +23,6 @@ make chaos_nohalf

 ## Try:

-
 ```sh
 ./try.sh
 ```
@@ -78,7 +78,6 @@ What's the difference between this and `dlowe`?
 Did you spot the Easter egg there?


-
 ## Judges' remarks:

 Why could this this entry be considered a utility?  Well because it
@@ -24,7 +24,7 @@ convert ioccc_ray.ppm ioccc_ray.jpg
 and then view `ioccc_ray.jpg` in a graphics viewer, editor or web browser.


-### Try:
+## Try:

 If you have `xv(1)` you can do:

@@ -149,7 +149,7 @@ for more details.</p>
 if you have ImageMagick installed, you can convert it to a jpeg:</p>
 <div class="sourceCode" id="cb3"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="ex">convert</span> ioccc_ray.ppm ioccc_ray.jpg</span></code></pre></div>
 <p>and then view <code>ioccc_ray.jpg</code> in a graphics viewer, editor or web browser.</p>
-<h3 id="try">Try:</h3>
+<h2 id="try">Try:</h2>
 <p>If you have <code>xv(1)</code> you can do:</p>
 <div class="sourceCode" id="cb4"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./gavare</span> <span class="kw">|</span> <span class="ex">xv</span> <span class="at">-</span></span></code></pre></div>
 <p>to not worry about writing it to a file and just viewing the image it creates.</p>
@@ -34,7 +34,6 @@ We recommend you input for the filename `example.gif` and for the string
 a loop until you answer that you do not wish to make another.


-
 ## Judges' remarks:

 This entry uses a very user-friendly representation of the font
@@ -38,7 +38,6 @@ Incorrect formulas will ungracefully crash the program.
 ```


-
 ## Alternate code:

 This alternate code lets you specify the width and height of the image as well
@@ -4,6 +4,7 @@
 make
 ```

+
 ### Bugs and (Mis)features:

 The current status of this entry is:
@@ -1,5 +1,6 @@
 # Contributor Covenant Code of Conduct

+
 ## Our Pledge

 We as members, contributors, and leaders pledge to make participation in our
@@ -12,6 +13,7 @@ and orientation.
 We pledge to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.

+
 ## Our Standards

 Examples of behavior that contributes to a positive environment for our
@@ -36,6 +38,7 @@ Examples of unacceptable behavior include:
 * Other conduct which could reasonably be considered inappropriate in a
  professional setting

+
 ## Enforcement Responsibilities

 Community leaders are responsible for clarifying and enforcing our standards of
@@ -56,6 +59,7 @@ Examples of representing our community include using an official e-mail address,
 posting via an official social media account, or acting as an appointed
 representative at an online or offline event.

+
 ## Enforcement

 Instances of abusive, harassing, or otherwise unacceptable behavior may be
@@ -66,11 +70,13 @@ All complaints will be reviewed and investigated promptly and fairly.
 All community leaders are obligated to respect the privacy and security of the
 reporter of any incident.

+
 ## Enforcement Guidelines

 Community leaders will follow these Community Impact Guidelines in determining
 the consequences for any action they deem in violation of this Code of Conduct:

+
 ### 1. Correction

 **Community Impact**: Use of inappropriate language or other behavior deemed
@@ -80,6 +86,7 @@ unprofessional or unwelcome in the community.
 clarity around the nature of the violation and an explanation of why the
 behavior was inappropriate. A public apology may be requested.

+
 ### 2. Warning

 **Community Impact**: A violation through a single incident or series
@@ -92,6 +99,7 @@ includes avoiding interactions in community spaces as well as external channels
 like social media. Violating these terms may lead to a temporary or
 permanent ban.

+
 ### 3. Temporary Ban

 **Community Impact**: A serious violation of community standards, including
@@ -103,6 +111,7 @@ private interaction with the people involved, including unsolicited interaction
 with those enforcing the Code of Conduct, is allowed during this period.
 Violating these terms may lead to a permanent ban.

+
 ### 4. Permanent Ban

 **Community Impact**: Demonstrating a pattern of violation of community
@@ -112,6 +121,7 @@ individual, or aggression toward or disparagement of classes of individuals.
 **Consequence**: A permanent ban from any sort of public interaction within
 the community.

+
 ## Attribution

 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
@@ -13,7 +13,7 @@ for i in $(git ls-files '[0-9][0-9][0-9][0-9]/*README.md'); do
    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(To build):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Bugs and \(Mis\)features):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(To use):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
-    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Try):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
+    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Try):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Original code):?\n\n*([^\n])?/$1\n\n## $2:\n\n$3/' "$i"
    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Original build):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"
    perl -0777 -p -i -e 's/([^\n]\n)\n*##*[[:space:]]*(Original try):?\n\n*([^\n])?/$1\n\n### $2:\n\n$3/' "$i"