Landon Curt Noll
4ee4c731f7
While not strictly necessary, replacing the two ASCII tab characters in the markdown copyright comment makes it easier to detect problematic TAB indentation within markdown files. After this commit, only 90 markdown files have leading ASCII TAB characters. And again, while not strictly necessary, we can consider running expand on those 90 markdown files to see what effect that might have on the HTML files they produce. Replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters (the default action of the `expand(1)` tool) might have an negative effect on some HTML formatting where **hack-a-round** formatting was attempted to fix broken indentation caused by problematic ASCII TAB characters. Think of this as a baseline for evaluating leading TAB characters within markdown files. TODO: Consider either using `expand(1)` to replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters AND/OR modifying the appropriate `bin` tool to convert leading ASCII TAB characters into multiples of 8 ASCII SPACE characters.
1.2 KiB
1.2 KiB
To build:
make all
On System V systems, we had to compile with -Dindex=strchr.
To compile on a 16 bit machine, change 300000 to 30000.
To use:
./heckbert col < file
where col is the number of columns to fold at and file is the file to fold.
Try:
./try.sh
Judges' remarks:
Folding at the wrong length may be equivalent to a "Spindle or Mutilate" operation. For example:
./heckbert 40 < heckbert.c > ph.c ; make ph ; ./ph 20 < heckbert.c > bar.c ; make bar
Try not to Fold, Spindle or Mutilate files. :-)
The judges used this program to fold up very long lines which the
BSD fold(1) was unable to process. This program has been added to
the contest tool chest.
Author's remarks:
No remarks were provided by the author.