ASCIIDOC and ASCIIDOC_MAN have been added, which default to the
(Python-based) reference implementation, but may be changed to
asciidoctor simply.
The manpages have been modified to use single-line section headings
for AsciiDoctor compatibility.
PORT is too generic, especially if refering to TCP/UDP ports, and if
those are set, the freedoom script may not work properly. DOOMPORT is
a reasonable alternative.
Non-reference AsciiDoc implementations such as AsciiDoctor (used by
GitHub) or even the simplistic parser in loccount choke up on these
characters for different reasons. AsciiDoctor doesn’t seem to even
parse them, displaying them as-is and not with emphasized text.
loccount would get hung up on possessives, expecting a terminating
character for emphasis that never comes.
Annoying, but easy to work around. the curly ’ character can be used
for possessives and _underscores_ can be used for emphasis.
The tags are shorthand for the license of each file and avoid
copying the full license text into each one (and avoids having
to manually update the dates in each one...).
GitHub’s AsciiDoc parser barfs on the standard AsciiDoc syntax to
represent such characters with only ASCII… Well, everybody should
support UTF‐8 these days. Let’s just use these directly.
Pretty basic shell script for finding a port and launching it
automatically. It's nothing overly fancy, but shell portability is
strived for, since it should be capable of launching no matter what
operating system is in use, it should not use anything more advanced
than is available in Bourn shell/POSIX (no ksh/bash extensions).
Mike Swanson