Attempt to fix alignment issue in 2020/ferguson2
It seems like the problem might have been because before opening a pull request the old file is viewed and the format was not correct there. Or it might be I did something wrong. Hopefully this resolves the issue.
This commit is contained in:
1 parent
8d73642d96
commit
c08f8f15a0
1 file changed
+13
-11
+13
-11
@@ -46,7 +46,7 @@ make
|
|||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
**NOTE**: in [recode](recode.c) no spaces between options and option arguments are allowed.
|
**NOTE**: in `recode` no spaces between options and option arguments are allowed.
|
||||||
|
|
||||||
## Try:
|
## Try:
|
||||||
|
|
||||||
@@ -100,10 +100,12 @@ There is a good deal of useful documentation that is provided with this entry:
|
|||||||
|
|
||||||
* [enigma.1](enigma.1) - A useful man page for this entry. To render, try:
|
* [enigma.1](enigma.1) - A useful man page for this entry. To render, try:
|
||||||
|
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
man ./enigma.1
|
man ./enigma.1
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
* [recode.html][] (or [recode.md](recode.md) if reading on GitHub)
|
* [recode.html][] (or [recode.md](recode.md) if reading on GitHub)
|
||||||
- Some useful information about [recode.c](recode.c)
|
- Some useful information about [recode.c](recode.c)
|
||||||
|
|
||||||
@@ -536,8 +538,8 @@ ended his life. (I later made a bug fix but I consider this inconsequential).
|
|||||||
As for [recode.c][] though I really love this:
|
As for [recode.c][] though I really love this:
|
||||||
|
|
||||||
```c
|
```c
|
||||||
/\
|
/\
|
||||||
/ This is *not* what you think:
|
/ This is *not* what you think:
|
||||||
```
|
```
|
||||||
|
|
||||||
...because it seems so wrong in C code at first glance. Also what does the
|
...because it seems so wrong in C code at first glance. Also what does the
|
||||||
@@ -601,14 +603,14 @@ when reading in settings via the `-R` option which I explain in the
|
|||||||
letters can connect to A or B. Earlier there wasn't proper detection and this
|
letters can connect to A or B. Earlier there wasn't proper detection and this
|
||||||
caused invalid output.
|
caused invalid output.
|
||||||
|
|
||||||
> Why only 10 pairs when the German alphabet has 26 letters (the Enigma did not
|
Why only 10 pairs when the German alphabet has 26 letters (the Enigma did
|
||||||
have the Eszett or the umlauts and in any case there is some disagreement about
|
not have the Eszett or the umlauts and in any case there is some
|
||||||
these being part of the alphabet; anyway for umlauts one can add an E after the
|
disagreement about these being part of the alphabet; anyway for umlauts one
|
||||||
letter and for the Eszett you can use 'ss' or 'SS' which is what they did)? It's
|
can add an E after the letter and for the Eszett you can use 'ss' or 'SS'
|
||||||
theoretically possible to have 13 but the Enigma typically had 10 pairs. It's
|
which is what they did)? It's theoretically possible to have 13 but the
|
||||||
easy enough to update my entry to do this once you de-obfuscate it but I'm not
|
Enigma typically had 10 pairs. It's easy enough to update my entry to do
|
||||||
helping there (and in fact I don't think I could any more even if I wanted to -
|
this once you de-obfuscate it but I'm not helping there (and in fact I don't
|
||||||
at least not easily).
|
think I could any more even if I wanted to - at least not easily).
|
||||||
|
|
||||||
* It does not obviously have the clicking sound associated with the moving
|
* It does not obviously have the clicking sound associated with the moving
|
||||||
parts of the real machine. I think it would be annoying to have this as it
|
parts of the real machine. I think it would be annoying to have this as it
|
||||||
|
|||||||
Reference in new issue
Block a user