fix more broken markdown links
Fixed stuff we broke by mistake, previously. Ran `make www` to perform the above. TODO: Fix stuff we broke by mistake doing the above. TODO: Fix more broken markdown links.
This commit is contained in:
Landon Curt Noll committed
1 parent
4f95e3f3d6
commit
8bca099534
62 files changed
+181
-168
No files matched your search
@@ -452,9 +452,9 @@ For examples using it (and a delicious challenge) see [recode.html][] (or
|
||||
### A parser subtlety that could cause confusion
|
||||
</div>
|
||||
|
||||
The parser is in a sense rather rudimentary but allows for both interactive and
|
||||
automatic (e.g. via the [recode]((%%REPO_URL%%/2020/ferguson2/recode.c) program) input. This does mean that
|
||||
something like the following can happen:
|
||||
The parser is in a sense rather rudimentary but allows for both interactive and automatic
|
||||
(e.g., via the [recode](%%REPO_URL%%/2020/ferguson2/recode.c) program) input.
|
||||
This does mean that something like the following can happen:
|
||||
|
||||
``` <!---sh-->
|
||||
$ ./prog -
|
||||
|
||||
@@ -707,9 +707,9 @@ make it more flexible by a wrapper program.</p>
|
||||
<div id="parsersubtlety">
|
||||
<h3 id="a-parser-subtlety-that-could-cause-confusion">A parser subtlety that could cause confusion</h3>
|
||||
</div>
|
||||
<p>The parser is in a sense rather rudimentary but allows for both interactive and
|
||||
automatic (e.g. via the <a href="(https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/recode.c)%20program">recode</a> input. This does mean that
|
||||
something like the following can happen:</p>
|
||||
<p>The parser is in a sense rather rudimentary but allows for both interactive and automatic
|
||||
(e.g., via the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/recode.c">recode</a> program) input.
|
||||
This does mean that something like the following can happen:</p>
|
||||
<pre><code> $ ./prog -
|
||||
Ring 1: 1AB
|
||||
Setting 1: Position 1: Ring 2: 2CD
|
||||
|
||||
@@ -458,8 +458,8 @@ if you don’t give the option to read in a file for input.</p>
|
||||
Plugboard pair #09: RU
|
||||
Plugboard pair #10: VG
|
||||
1WX5AK4RE1XEHJSAPYCIZBWDQNRUVGIOCCC</code></pre>
|
||||
<p>Though you won’t find some of those strings in [recode.c]((https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/recode.c) or
|
||||
[prog.c]((https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/prog.c). Yes the <code>WAR</code> for the Ringstellung (Ring settings) is an
|
||||
<p>Though you won’t find some of those strings in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/recode.c">recode.c</a> or
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/prog.c">prog.c</a>. Yes the <code>WAR</code> for the Ringstellung (Ring settings) is an
|
||||
amusing coincidence <em>but it really did happen!</em></p>
|
||||
<p>As for <code>-f</code> the contents would be output with the settings e.g. to pipe to
|
||||
<code>prog</code> itself (as if you redirected the file contents to the Enigma machine for
|
||||
@@ -585,7 +585,7 @@ pair</a>; this can be done in
|
||||
a number of ways but two dots is one. Notice also that it’s in a different order
|
||||
than the simulator: because with the size restrictions on my entry I saved bytes
|
||||
by using the same loop where I could. It just felt more natural to have them
|
||||
grouped together in a configurator for the [simulator]((https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/prog.c).</p>
|
||||
grouped together in a configurator for the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson2/prog.c">simulator</a>.</p>
|
||||
<pre><code> $ echo 1AA2AA3AA2ABCD..EFGHIJKLMNOPQRIOCCC | ./prog - 2>/dev/null
|
||||
HQNVO
|
||||
$ echo 1AA2AA3AA2ABCD..EFGHIJKLMNOPQRIOCCC | ./prog - 2>/dev/null | echo 1AA2AA3AA2ABCD..EFGHIJKLMNOPQRHQNVO | ./prog - 2>/dev/null
|
||||
|
||||
@@ -18,7 +18,7 @@ have to if you don't wish to.
|
||||
- [Only write config file](#onlyconfig)
|
||||
- [Reusing a configuration](#reuseconfig)
|
||||
- [Write config file, read data file and pass to Enigma simulator](#passtoenigma)
|
||||
- [Piping directly to the Enigma code once (with randomised settings, saved)](#directlytoenigma)
|
||||
- [Piping directly to the Enigma code once (with randomised settings, saved)](#directlytoenigma)
|
||||
- [Usage conclusion](#conclusion)
|
||||
- [Example additions](#additions)
|
||||
- [Example uses](#exampleuses)
|
||||
@@ -97,8 +97,8 @@ if you don't give the option to read in a file for input.
|
||||
1WX5AK4RE1XEHJSAPYCIZBWDQNRUVGIOCCC
|
||||
```
|
||||
|
||||
Though you won't find some of those strings in [recode.c]((%%REPO_URL%%/2020/ferguson2/recode.c) or
|
||||
[prog.c]((%%REPO_URL%%/2020/ferguson2/prog.c). Yes the `WAR` for the Ringstellung (Ring settings) is an
|
||||
Though you won't find some of those strings in [recode.c](%%REPO_URL%%/2020/ferguson2/recode.c) or
|
||||
[prog.c](%%REPO_URL%%/2020/ferguson2/prog.c). Yes the `WAR` for the Ringstellung (Ring settings) is an
|
||||
amusing coincidence *but it really did happen!*
|
||||
|
||||
As for `-f` the contents would be output with the settings e.g. to pipe to
|
||||
@@ -265,7 +265,7 @@ pair](https://www.cryptomuseum.com/crypto/enigma/i/sb.htm); this can be done in
|
||||
a number of ways but two dots is one. Notice also that it's in a different order
|
||||
than the simulator: because with the size restrictions on my entry I saved bytes
|
||||
by using the same loop where I could. It just felt more natural to have them
|
||||
grouped together in a configurator for the [simulator]((%%REPO_URL%%/2020/ferguson2/prog.c).
|
||||
grouped together in a configurator for the [simulator](%%REPO_URL%%/2020/ferguson2/prog.c).
|
||||
|
||||
``` <!---sh-->
|
||||
$ echo 1AA2AA3AA2ABCD..EFGHIJKLMNOPQRIOCCC | ./prog - 2>/dev/null
|
||||
|
||||
Reference in new issue
Block a user