Expand all leading tabs in markdown files
Given how problematic leading tabs in markdown files can be,
we have expanded all leading tabs in markdown files by:
```sh
find * -type f -name '*.md' -print |
while read -r file; do
rm -f "$file.tmp" ;
expand < "$file" > "$file.tmp" ;
mv -f -v "$file.tmp" "$file" ;
done
```
Given the previous changes to `bin/pandoc-wrapper.sh` and other recent
commits and recent pull requests, the were were **NO** changes to
any HTML files. This is a **good thing** as the expression goes.
No there are no leading tabs in any markdown files.
A check to catch any re-introduction of leading tabs
into any markdown file is on the way.
BTW: We do not have anything against leading tabs in files,
even though we have had to deal with their impact on forming
HTML from markdown files (as well as the calc source code).
It is just that this is one of those cases where tabs conflict
(sometimes caused by people wanting to change the classic
8-space tab model) with a desired outcome.
Perform `make www` to perform the above and test under macOS.
This commit is contained in:
Landon Curt Noll committed
1 parent
bf28cac593
commit
7712db4a17
117 files changed
+1758
-1758
No files matched your search
@@ -53,13 +53,13 @@ characters (semaphore smileys, if you will). For example, given the
|
||||
input "Hello, world!", the output will be:
|
||||
|
||||
```
|
||||
<> <> <> <> <> <>
|
||||
<> <> <> <> <> <>
|
||||
_() ()/ ()/ ()/ _\) () (/_ _\)
|
||||
[] /^ |^^ /^^ /^^ [] ^^ |^^| ^^ [] [] ^^
|
||||
<>[ [][ <>][ <>][ ][ [][] ][ ][
|
||||
|
||||
|
||||
<> []
|
||||
<> []
|
||||
_()_ ()/ |() ()
|
||||
[] ^^ [] /^^ ^^| |^^|
|
||||
][ <>][ ][] [][]
|
||||
|
||||
@@ -33,7 +33,7 @@ The author recommended on linux/x86, glibc 2.0, libc4/5:
|
||||
|
||||
``` <!---make-->
|
||||
bmeyer: bmeyer.c
|
||||
CC -DY="__setfpucw(0x127f)" -O6 $? -o $@ -lm
|
||||
CC -DY="__setfpucw(0x127f)" -O6 $? -o $@ -lm
|
||||
```
|
||||
|
||||
However many compilers use `-O3` as the maximum level for `-O` optimization.
|
||||
@@ -42,7 +42,7 @@ And on linux/x86, glibc 2.1:
|
||||
|
||||
``` <!---make-->
|
||||
bmeyer: bmeyer.c
|
||||
gcc -DY='int x=0x127f; __asm__ ("fldcw %0" : : "m" (*&x))' $? -o $@ -lm
|
||||
gcc -DY='int x=0x127f; __asm__ ("fldcw %0" : : "m" (*&x))' $? -o $@ -lm
|
||||
```
|
||||
|
||||
Compile with the maximum possible optimization on your system.
|
||||
|
||||
+12
-12
@@ -76,9 +76,9 @@ This program understands the following `dc(1)` commands:
|
||||
```
|
||||
p prints the top stack value without altering the stack.
|
||||
P prints the top stack value, removing it from the stack, and
|
||||
doesn't print a trailing newline.
|
||||
doesn't print a trailing newline.
|
||||
f prints the contents of the stack, one number per line,
|
||||
without modifying it.
|
||||
without modifying it.
|
||||
c clears the stack.
|
||||
d pushes a copy of the top stack value onto the stack.
|
||||
r reverses the order of the top two stack values.
|
||||
@@ -89,14 +89,14 @@ And the following arithmetic operators are supported:
|
||||
```
|
||||
+ Pops 2 values and pushes their sum.
|
||||
- Pops 2 values and pushes the result of subtracting the first
|
||||
from the second.
|
||||
from the second.
|
||||
* Pops 2 values and pushes their product.
|
||||
/ Pops 2 values and pushes the result of dividing the second
|
||||
by the first.
|
||||
by the first.
|
||||
^ Pops 2 values and pushes the result of raising the second
|
||||
to the power of the first.
|
||||
to the power of the first.
|
||||
% Pops 2 values and pushes the remainder of the division that
|
||||
/ would do.
|
||||
/ would do.
|
||||
```
|
||||
|
||||
The precision and range are double, like it or not, except that the
|
||||
@@ -113,14 +113,14 @@ or EOF is encountered.
|
||||
### Diagnostics:
|
||||
|
||||
```
|
||||
"stack empty" Not enough on the stack for the requested command
|
||||
"divide by zero" Attempt to divide by zero
|
||||
"unimplemented" Invalid input
|
||||
"stack empty" Not enough on the stack for the requested command
|
||||
"divide by zero" Attempt to divide by zero
|
||||
"unimplemented" Invalid input
|
||||
|
||||
Floating point exception (core dumped) (or something to that effect)
|
||||
Bug in Perl_sv_upgrade causes this in some cases when
|
||||
the results of an operation are really huge (> 10^308)
|
||||
This bug appears to be fixed in perl5.6.0
|
||||
Bug in Perl_sv_upgrade causes this in some cases when
|
||||
the results of an operation are really huge (> 10^308)
|
||||
This bug appears to be fixed in perl5.6.0
|
||||
```
|
||||
|
||||
|
||||
|
||||
@@ -115,13 +115,13 @@ from inside the monitor whilst standing on your head. In case of
|
||||
confusion, please consult the following chart (\*):
|
||||
|
||||
```
|
||||
N
|
||||
^
|
||||
|
|
||||
E <---+---> W
|
||||
|
|
||||
v
|
||||
S
|
||||
N
|
||||
^
|
||||
|
|
||||
E <---+---> W
|
||||
|
|
||||
v
|
||||
S
|
||||
```
|
||||
|
||||
(\*) Not to scale.
|
||||
@@ -316,7 +316,7 @@ common tricks. Taken through the standard rounds listed in the
|
||||
`select()`, the following may suffice as an additional compiler argument:
|
||||
|
||||
```
|
||||
-Dusleep={time_t v[2]={0,10000};select(0,0,0,0,v);}
|
||||
-Dusleep={time_t v[2]={0,10000};select(0,0,0,0,v);}
|
||||
```
|
||||
|
||||
`gcc` complains about "unreachable code at beginning of switch
|
||||
|
||||
+33
-33
@@ -120,9 +120,9 @@ I claim, by letters patently absurd:
|
||||
operations.
|
||||
|
||||
6. The method of claim 1, further comprising a method where
|
||||
* strings are encrypted in a manner suitable as C strings, and
|
||||
* 7-bit ASCII characters with uniform distribution are maximally packed
|
||||
subject to the restriction that each byte is not countable
|
||||
* strings are encrypted in a manner suitable as C strings, and
|
||||
* 7-bit ASCII characters with uniform distribution are maximally packed
|
||||
subject to the restriction that each byte is not countable
|
||||
|
||||
7. A method for a computer-based system that uses a single shared code
|
||||
sequence to either sum a plurality of bits in an N-bit word or reverses
|
||||
@@ -134,46 +134,46 @@ I claim, by letters patently absurd:
|
||||
#### FIG 1.
|
||||
|
||||
```
|
||||
+--+--+--+--+--+--+--+--+
|
||||
|32| |31| |30| |29| |
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| |28| |27| |26| |25|
|
||||
+--+--+--+--+--+--+--+--+
|
||||
|24| |23| |22| |21| |
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| |20| |19| |18| |17|
|
||||
+--+--+--+--+--+--+--+--+
|
||||
|16| |15| |14| |13| |
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| |12| |11| |10| | 9|
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| 8| | 7| | 6| | 5| |
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| | 4| | 3| | 2| | 1|
|
||||
+--+--+--+--+--+--+--+--+
|
||||
+--+--+--+--+--+--+--+--+
|
||||
|32| |31| |30| |29| |
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| |28| |27| |26| |25|
|
||||
+--+--+--+--+--+--+--+--+
|
||||
|24| |23| |22| |21| |
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| |20| |19| |18| |17|
|
||||
+--+--+--+--+--+--+--+--+
|
||||
|16| |15| |14| |13| |
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| |12| |11| |10| | 9|
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| 8| | 7| | 6| | 5| |
|
||||
+--+--+--+--+--+--+--+--+
|
||||
| | 4| | 3| | 2| | 1|
|
||||
+--+--+--+--+--+--+--+--+
|
||||
```
|
||||
|
||||
#### FIG. 2.
|
||||
|
||||
```
|
||||
1 0
|
||||
\ /
|
||||
.
|
||||
/ \
|
||||
3 2
|
||||
1 0
|
||||
\ /
|
||||
.
|
||||
/ \
|
||||
3 2
|
||||
```
|
||||
|
||||
#### FIG. 3.
|
||||
|
||||
```
|
||||
o o X . 29
|
||||
o . . . 25
|
||||
o . . o 21
|
||||
. o . o 17
|
||||
x . . . 13
|
||||
. . x . 9
|
||||
x x . . 5
|
||||
x x O x 1
|
||||
o o X . 29
|
||||
o . . . 25
|
||||
o . . o 21
|
||||
. o . o 17
|
||||
x . . . 13
|
||||
. . x . 9
|
||||
x x . . 5
|
||||
x x O x 1
|
||||
```
|
||||
|
||||
#### FIG. 4
|
||||
|
||||
Reference in new issue
Block a user