improved indentation and whitespace for markdown code blocks

All code blocks in markdown have been intended by at least 4 spaces.

We add `--tab-stop=8` to all `pandoc(1)` executions in order to set
a better tab stop indentation, especially for tab intended code blocks.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.5.3 2024-03-26"
to "1.6 2024-03-31".

Fixed `1991/brnstnd/sorta.README.md` so that the sorta code
is code blocks.

Removed unneeded paragraph group in copyright in `inc/footer.default.html`.

Fixed excess whitespace after list Author on entry `index.html` page.

Changed `bin/output-index-author.sh` VERSION from "1.5.2 2024-03-26"
to "1.6 2024-03-31".

Performed `make www` to perform the above and test under macOS.

TODO: Fix the problem of the initial line of code being extra intended.
TODO: Fix excess whitespace around code that is inline.
This commit is contained in:
Landon Curt Noll committed 2024-04-01 04:48:48 -07:00
1 parent b84c27ce02
commit a996f8d2b8
734 files changed
+16723 -16963

No files matched your search

+10 -10
View File
@@ -1,7 +1,7 @@
## To build:
```sh
make
make
```
NOTE: we disable the optimiser because this program has problems with it
@@ -13,7 +13,7 @@ enabled.
The current status of this entry is:
```
STATUS: INABIAF - please **DO NOT** fix
STATUS: INABIAF - please **DO NOT** fix
```
For more detailed information see [2019 karns bugs](../../bugs.html#2019_karns).
@@ -22,13 +22,13 @@ For more detailed information see [2019 karns bugs](../../bugs.html#2019_karns).
## To use:
```sh
./prog < textfile_that_fits_on_the_screen
./prog < textfile_that_fits_on_the_screen
```
You might want to type:
```sh
reset
reset
```
after running the program to restore the terminal to its previous state.
@@ -37,13 +37,13 @@ after running the program to restore the terminal to its previous state.
## Try:
```sh
./try.sh
./try.sh
```
If you have more time you might want to try:
```sh
./prog < README.md
./prog < README.md
```
@@ -83,7 +83,7 @@ connected with anything.
This program usually compiles under both GCC and clang. Build with:
```sh
$(CC) -std=c99 -o tbfs prog.c
$(CC) -std=c99 -o tbfs prog.c
```
where `$(CC)` is cc, gcc, clang, or some other C compiler.
@@ -91,14 +91,14 @@ where `$(CC)` is cc, gcc, clang, or some other C compiler.
You can then run it with:
```sh
cat <input file> | ./tbfs
cat <input file> | ./tbfs
```
Examples:
```sh
./tbfs < maze
./tbfs < prog.c
./tbfs < maze
./tbfs < prog.c
```
### Issues