improved indentation and whitespace for markdown code blocks
All code blocks in markdown have been intended by at least 4 spaces. We add `--tab-stop=8` to all `pandoc(1)` executions in order to set a better tab stop indentation, especially for tab intended code blocks. Changed `bin/pandoc-wrapper.sh` VERSION from "1.5.3 2024-03-26" to "1.6 2024-03-31". Fixed `1991/brnstnd/sorta.README.md` so that the sorta code is code blocks. Removed unneeded paragraph group in copyright in `inc/footer.default.html`. Fixed excess whitespace after list Author on entry `index.html` page. Changed `bin/output-index-author.sh` VERSION from "1.5.2 2024-03-26" to "1.6 2024-03-31". Performed `make www` to perform the above and test under macOS. TODO: Fix the problem of the initial line of code being extra intended. TODO: Fix excess whitespace around code that is inline.
This commit is contained in:
Landon Curt Noll committed
1 parent
b84c27ce02
commit
a996f8d2b8
734 files changed
+16723
-16963
No files matched your search
+15
-15
@@ -1,21 +1,21 @@
|
||||
## To build:
|
||||
|
||||
```sh
|
||||
make
|
||||
make
|
||||
```
|
||||
|
||||
|
||||
## To use:
|
||||
|
||||
```sh
|
||||
./vik [file.map]
|
||||
./vik [file.map]
|
||||
```
|
||||
|
||||
|
||||
## Try:
|
||||
|
||||
```sh
|
||||
./vik maze.map
|
||||
./vik maze.map
|
||||
```
|
||||
|
||||
|
||||
@@ -61,14 +61,14 @@ libraries](https://en.wikipedia.org/wiki/Xlib) if necessary. The program takes
|
||||
three options which have to be typed in a specific order as described below.
|
||||
|
||||
```sh
|
||||
./vik [-w <width>] [mapfile]
|
||||
./vik [-w <width>] [mapfile]
|
||||
```
|
||||
|
||||
where:
|
||||
|
||||
```
|
||||
width - Specifies the width of the window
|
||||
mapfile - Filename containing a map
|
||||
width - Specifies the width of the window
|
||||
mapfile - Filename containing a map
|
||||
```
|
||||
|
||||
#### Examples
|
||||
@@ -76,20 +76,20 @@ mapfile - Filename containing a map
|
||||
Start the engine using a built in labyrinth and texture bitmaps:
|
||||
|
||||
```sh
|
||||
./vik
|
||||
./vik
|
||||
```
|
||||
|
||||
Start the engine and loads the labyrinth defined in the file
|
||||
[maze.map](maze.map):
|
||||
|
||||
```sh
|
||||
./vik maze.map
|
||||
./vik maze.map
|
||||
```
|
||||
|
||||
Start the engine using [maze.map](maze.map) in a window that is 400 pixels wide:
|
||||
|
||||
```sh
|
||||
./vik -w 400 maze.map
|
||||
./vik -w 400 maze.map
|
||||
```
|
||||
|
||||
Note that the `mapfile` has to be the last argument and the `-w` option if present
|
||||
@@ -107,12 +107,12 @@ engine what bitmap texture file to use. The `*` character lets the engine know
|
||||
where to position the user. The example below shows how a map file can look:
|
||||
|
||||
```
|
||||
aaaaaaaaaaaaa
|
||||
a a
|
||||
a * a
|
||||
a bbbb cccccccc
|
||||
c c
|
||||
cccccccccccccccccccc
|
||||
aaaaaaaaaaaaa
|
||||
a a
|
||||
a * a
|
||||
a bbbb cccccccc
|
||||
c c
|
||||
cccccccccccccccccccc
|
||||
```
|
||||
|
||||
The engine loads the map, and creates walls. When a character in the range `a-z`
|
||||
|
||||
+16
-17
@@ -132,8 +132,7 @@
|
||||
<h2 id="author"><a name="author"></a>Author:</h2>
|
||||
<ul>
|
||||
<li>Name: <a href="../../authors.html#Daniel_Vik">Daniel Vik</a><br>
|
||||
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)
|
||||
<br><br></li>
|
||||
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)</li>
|
||||
</ul>
|
||||
|
||||
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
|
||||
@@ -142,11 +141,11 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
|
||||
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
|
||||
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span></span></code></pre></div>
|
||||
<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a> <span class="fu">make</span></span></code></pre></div>
|
||||
<h2 id="to-use">To use:</h2>
|
||||
<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./vik</span> <span class="pp">[</span><span class="ss">file.map</span><span class="pp">]</span></span></code></pre></div>
|
||||
<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a> <span class="ex">./vik</span> <span class="pp">[</span><span class="ss">file.map</span><span class="pp">]</span></span></code></pre></div>
|
||||
<h2 id="try">Try:</h2>
|
||||
<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">./vik</span> maze.map</span></code></pre></div>
|
||||
<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">./vik</span> maze.map</span></code></pre></div>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>An amazing use of the X libraries with twisty code passages, all different. One
|
||||
risks running in code path circles as <code>main()</code> is called again and again. Be
|
||||
@@ -178,18 +177,18 @@ backward).</li>
|
||||
<p>Compile the source code and link in <a href="https://en.wikipedia.org/wiki/Xlib">X
|
||||
libraries</a> if necessary. The program takes
|
||||
three options which have to be typed in a specific order as described below.</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">./vik</span> [-w <span class="op"><</span>width<span class="op">></span>] <span class="pp">[</span><span class="ss">mapfile</span><span class="pp">]</span></span></code></pre></div>
|
||||
<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">./vik</span> [-w <span class="op"><</span>width<span class="op">></span>] <span class="pp">[</span><span class="ss">mapfile</span><span class="pp">]</span></span></code></pre></div>
|
||||
<p>where:</p>
|
||||
<pre><code>width - Specifies the width of the window
|
||||
mapfile - Filename containing a map</code></pre>
|
||||
<pre><code> width - Specifies the width of the window
|
||||
mapfile - Filename containing a map</code></pre>
|
||||
<h4 id="examples">Examples</h4>
|
||||
<p>Start the engine using a built in labyrinth and texture bitmaps:</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">./vik</span></span></code></pre></div>
|
||||
<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">./vik</span></span></code></pre></div>
|
||||
<p>Start the engine and loads the labyrinth defined in the file
|
||||
<a href="maze.map">maze.map</a>:</p>
|
||||
<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">./vik</span> maze.map</span></code></pre></div>
|
||||
<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">./vik</span> maze.map</span></code></pre></div>
|
||||
<p>Start the engine using <a href="maze.map">maze.map</a> in a window that is 400 pixels wide:</p>
|
||||
<div class="sourceCode" id="cb8"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./vik</span> <span class="at">-w</span> 400 maze.map</span></code></pre></div>
|
||||
<div class="sourceCode" id="cb8"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a> <span class="ex">./vik</span> <span class="at">-w</span> 400 maze.map</span></code></pre></div>
|
||||
<p>Note that the <code>mapfile</code> has to be the last argument and the <code>-w</code> option if present
|
||||
has to be the first. The map definition files and the bitmap files should be
|
||||
located in the current directory.</p>
|
||||
@@ -199,12 +198,12 @@ located in the current directory.</p>
|
||||
ASCII text file where lower case letters represent walls. The letter tells the
|
||||
engine what bitmap texture file to use. The <code>*</code> character lets the engine know
|
||||
where to position the user. The example below shows how a map file can look:</p>
|
||||
<pre><code>aaaaaaaaaaaaa
|
||||
a a
|
||||
a * a
|
||||
a bbbb cccccccc
|
||||
c c
|
||||
cccccccccccccccccccc</code></pre>
|
||||
<pre><code> aaaaaaaaaaaaa
|
||||
a a
|
||||
a * a
|
||||
a bbbb cccccccc
|
||||
c c
|
||||
cccccccccccccccccccc</code></pre>
|
||||
<p>The engine loads the map, and creates walls. When a character in the range <code>a-z</code>
|
||||
is found, the engine will load the corresponding texture bitmap. The bitmap file
|
||||
must be named <code>*.bmp</code> where <code>*</code> is substituted with the letter of the wall in
|
||||
|
||||
Reference in new issue
Block a user