improve how markdown code language is commented

We added a space between the markdown triple code mark
and language that was enclosed in HTML comments.

So a line of the form:

````
```<!---c--->
````

became:

````
``` <!---c--->
````

This was done to **help** some code see that the HTML comment
string was not a markdown code specifier.   Not all code
understands this after this changed.  For example, `pandoc(1)`
still forms HTML classes of the form "&lt;!---c--&gt;"
when it encounters the above mentioned change.

We also fixed a problem with `2019/dogon/README.md` regarding
a markdown code block.

We also fixed a problem with `2020/yang/README.md` regarding
a markdown code block.
This commit is contained in:
Landon Curt Noll committed 2024-04-12 11:45:50 -07:00
1 parent c549f6585e
commit 3ddbac9e6b
357 files changed
+2432 -2399

No files matched your search

+14 -14
View File
@@ -1,6 +1,6 @@
## To build:
```<!---sh-->
``` <!---sh-->
make
```
@@ -21,7 +21,7 @@ For more detailed information see [2001 kev bugs](../../bugs.html#2001_kev).
## To use:
```<!---sh-->
``` <!---sh-->
./kev # in one terminal
./kev hostname # in another terminal
@@ -32,7 +32,7 @@ NOTE: each player's paddle is at the bottom and the opponent at the top.
## Try:
```<!---sh-->
``` <!---sh-->
./kev # in one terminal
./kev localhost # in another terminal on the same host
@@ -41,13 +41,13 @@ NOTE: each player's paddle is at the bottom and the opponent at the top.
If you need to change the speed you can reconfigure it like (say
for over a network and not the same host):
```<!---sh-->
``` <!---sh-->
make clobber SPEED=50 all # original default value which is very fast
```
If you wish to change the port you can do so like:
```<!---sh-->
``` <!---sh-->
make clobber PORT=3773 all
```
@@ -58,19 +58,19 @@ syscall with the `l_` macro, changing the `L` variable like one would `PORT`. Of
course you can do more than one at the same time. For instance to change the
speed and port:
```<!---sh-->
``` <!---sh-->
make clobber SPEED=512 PORT=3773 all
```
If you have `xterm` try on one system:
```<!---sh-->
``` <!---sh-->
xterm -geometry 80x40 -fg green -bg black -fn 9x15bold -e ./kev &
```
and then the other, the client system:
```<!---sh-->
``` <!---sh-->
xterm -geometry 80x40 -fg green -bg black -fn 9x15bold -e ./kev localhost&
```
@@ -85,7 +85,7 @@ awkward `,` and `.` keys to move your paddle.
### Alternate build:
```<!---sh-->
``` <!---sh-->
make alt
```
@@ -105,13 +105,13 @@ terminal?
If you have `xterm` try on one system:
```<!---sh-->
``` <!---sh-->
xterm -geometry 80x40 -fg green -bg black -fn 9x15bold -e ./kev.alt &
```
and then the other, the client system:
```<!---sh-->
``` <!---sh-->
xterm -geometry 80x40 -fg green -bg black -fn 9x15bold -e ./kev.alt localhost&
```
@@ -151,14 +151,14 @@ getting the ball past your opponent's paddle. It's pretty fun! :)
Run the server first without any command line arguments, i.e.
```<!---sh-->
``` <!---sh-->
./kev
```
Then run the client with a single command line argument which is
the name of the machine running the server, e.g.
```<!---sh-->
``` <!---sh-->
./kev localhost
```
@@ -169,7 +169,7 @@ blocked by a firewall.
Here's a good quick example to see it in action on your own
machine, assuming you have `Xwindows`:
```<!---sh-->
``` <!---sh-->
xterm -geometry 80x40 -fg green -bg black -fn 9x15bold -e ./kev &
xterm -geometry 80x40 -fg green -bg black -fn 9x15bold -e ./kev localhost&
```