improve list formatting in 2020/ferguson1 markdown files
This commit is contained in:
1 parent
78863e5311
commit
25eae4b2db
17 files changed
+119
-238
No files matched your search
+16
-16
@@ -130,24 +130,24 @@ you could look at my <a href="../ferguson1/prog.c">Snake entry ‘Don’t tread
|
||||
award</a> since it’s also there and not enciphered.</p>
|
||||
<p><a name="toc"></a></p>
|
||||
<ul>
|
||||
<li><p><a href="#recode">What is recode and why is it recommended?</a></p></li>
|
||||
<li><p><a href="#options">Options</a></p>
|
||||
<li><a href="#recode">What is recode and why is it recommended?</a></li>
|
||||
<li><a href="#options">Options</a>
|
||||
<ul>
|
||||
<li><p><a href="#samefile">Protecting against the same I/O file</a></p></li>
|
||||
<li><p><a href="#fileoptions">File options parser limitation</a></p></li>
|
||||
<li><p><a href="#validation"><code>-R</code> option validation?</a></p></li>
|
||||
<li><a href="#samefile">Protecting against the same I/O file</a></li>
|
||||
<li><a href="#fileoptions">File options parser limitation</a></li>
|
||||
<li><a href="#validation"><code>-R</code> option validation?</a></li>
|
||||
</ul></li>
|
||||
<li><p><a href="#pipingtorecode">Piping commands to recode</a></p></li>
|
||||
<li><p><a href="#pipingtoenigma">Piping recode to the Enigma simulator</a></p></li>
|
||||
<li><p><a href="#manuallytest">Manually test the recode program with the Enigma program</a></p></li>
|
||||
<li><p><a href="#onlyconfig">Only write config file</a></p></li>
|
||||
<li><p><a href="#reuseconfig">Reusing a configuration</a></p></li>
|
||||
<li><p><a href="#passtoenigma">Write config file, read data file and pass to Enigma simulator</a></p></li>
|
||||
<li><p><a href="#directlytoenigma">Piping directly to the Enigma code once (with randomised settings, saved)</a></p></li>
|
||||
<li><p><a href="#conclusion">Usage conclusion</a></p></li>
|
||||
<li><p><a href="#additions">Example additions</a></p></li>
|
||||
<li><p><a href="#exampleuses">Example uses</a></p></li>
|
||||
<li><p><a href="#cake">Deliciously Enigmatic: Double-layered Chocolate Fudge Cake</a></p></li>
|
||||
<li><a href="#pipingtorecode">Piping commands to recode</a></li>
|
||||
<li><a href="#pipingtoenigma">Piping recode to the Enigma simulator</a></li>
|
||||
<li><a href="#manuallytest">Manually test the recode program with the Enigma program</a></li>
|
||||
<li><a href="#onlyconfig">Only write config file</a></li>
|
||||
<li><a href="#reuseconfig">Reusing a configuration</a></li>
|
||||
<li><a href="#passtoenigma">Write config file, read data file and pass to Enigma simulator</a></li>
|
||||
<li><a href="#directlytoenigma">Piping directly to the Enigma code once (with randomised settings, saved)</a></li>
|
||||
<li><a href="#conclusion">Usage conclusion</a></li>
|
||||
<li><a href="#additions">Example additions</a></li>
|
||||
<li><a href="#exampleuses">Example uses</a></li>
|
||||
<li><a href="#cake">Deliciously Enigmatic: Double-layered Chocolate Fudge Cake</a></li>
|
||||
</ul>
|
||||
<h1 id="what-is-recode-and-why-is-it-recommended"><a name="recode" href="#toc">What is recode and why is it recommended?</a></h1>
|
||||
<p>To demonstrate how to and why you should use the <a href="recode.c">recode</a> program with
|
||||
|
||||
Reference in new issue
Block a user