changes to improve the general format of markdown files
This commit is contained in:
1 parent
6ab0485404
commit
dcd33ae8d5
25 files changed
+25
-26
No files matched your search
+1
-1
@@ -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
|
||||
|
||||
+1
-1
@@ -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"><</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 & 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">&&</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>
|
||||
|
||||
Reference in new issue
Block a user