fix many internal links

Fixed a number of internal links that need to
go to the GitHub site.

Ran `make www` to perform the above.
This commit is contained in:
Landon Curt Noll committed 2024-04-24 02:37:42 -07:00
1 parent b84f8cbe28
commit e7d69bc232
175 files changed
+645 -631

No files matched your search

+6 -6
View File
@@ -25,7 +25,7 @@ below for more details.
## Alternate code:
An alternate version of this entry, [prog.alt.c](prog.alt.c), is provided. As
An alternate version of this entry, [prog.alt.c](%%REPO_URL%%/2018/ciura/prog.alt.c), is provided. As
mentioned in the author's [remarks](#remarks), the alternate version lacks a
useful bug fix.
@@ -48,14 +48,14 @@ Use `prog.alt` as you would `prog` above.
./try.alt.sh
```
Do you spot the fix by running both [try.sh](try.sh) and
[try.alt.sh](try.alt.sh)?
Do you spot the fix by running both [try.sh](%%REPO_URL%%/2018/ciura/try.sh) and
[try.alt.sh](%%REPO_URL%%/2018/ciura/try.alt.sh)?
## Judges' remarks:
This text was processed by `prog`. You may get confused. We're not really sure:
[prog.c](prog.c) wasn't commented. Who has been thoroughly puzzled by `prog`?
[prog.c](%%REPO_URL%%/2018/ciura/prog.c) wasn't commented. Who has been thoroughly puzzled by `prog`?
Also how obfuscated is `prog`? Having been written in C, how large of a
vocabulary has it?
@@ -258,8 +258,8 @@ Return `abbreviation`.
### Remarks:
The judges found a bug in the handling of contractions: [prog.alt.c](prog.alt.c)
outputs "foo wasn'**[t bazzed]**". I fixed the bug in [prog.c](prog.c), making
The judges found a bug in the handling of contractions: [prog.alt.c](%%REPO_URL%%/2018/ciura/prog.alt.c)
outputs "foo wasn'**[t bazzed]**". I fixed the bug in [prog.c](%%REPO_URL%%/2018/ciura/prog.c), making
it output "foo **[wasn't bazzed]**" instead, and took the liberty to merge
one statement into a `for` loop inside its `main()` function.
+6 -6
View File
@@ -387,7 +387,7 @@ below for more details.</p>
<h2 id="try">Try:</h2>
<pre><code> ./try.sh</code></pre>
<h2 id="alternate-code">Alternate code:</h2>
<p>An alternate version of this entry, <a href="prog.alt.c">prog.alt.c</a>, is provided. As
<p>An alternate version of this entry, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/ciura/prog.alt.c">prog.alt.c</a>, is provided. As
mentioned in the author’s <a href="#remarks">remarks</a>, the alternate version lacks a
useful bug fix.</p>
<h3 id="alternate-build">Alternate build:</h3>
@@ -396,11 +396,11 @@ useful bug fix.</p>
<p>Use <code>prog.alt</code> as you would <code>prog</code> above.</p>
<h3 id="alternate-try">Alternate try:</h3>
<pre><code> ./try.alt.sh</code></pre>
<p>Do you spot the fix by running both <a href="try.sh">try.sh</a> and
<a href="try.alt.sh">try.alt.sh</a>?</p>
<p>Do you spot the fix by running both <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/ciura/try.sh">try.sh</a> and
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/ciura/try.alt.sh">try.alt.sh</a>?</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>This text was processed by <code>prog</code>. You may get confused. We’re not really sure:
<a href="prog.c">prog.c</a> wasn’t commented. Who has been thoroughly puzzled by <code>prog</code>?
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/ciura/prog.c">prog.c</a> wasn’t commented. Who has been thoroughly puzzled by <code>prog</code>?
Also how obfuscated is <code>prog</code>? Having been written in C, how large of a
vocabulary has it?</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
@@ -578,8 +578,8 @@ in the byte. Return <code>adverb</code>.</li>
Return <code>abbreviation</code>.</li>
</ul>
<h3 id="remarks">Remarks:</h3>
<p>The judges found a bug in the handling of contractions: <a href="prog.alt.c">prog.alt.c</a>
outputs “foo wasn’<strong>[t bazzed]</strong>”. I fixed the bug in <a href="prog.c">prog.c</a>, making
<p>The judges found a bug in the handling of contractions: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/ciura/prog.alt.c">prog.alt.c</a>
outputs “foo wasn’<strong>[t bazzed]</strong>”. I fixed the bug in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/ciura/prog.c">prog.c</a>, making
it output “foo <strong>[wasn’t bazzed]</strong>” instead, and took the liberty to merge
one statement into a <code>for</code> loop inside its <code>main()</code> function.</p>
<p>The program uses a 9,437,187-byte buffer so it probably will not run